messages
listlengths 3
3
| metadata
dict | subcategory
stringclasses 10
values |
|---|---|---|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"review_id\": \"REV-1521978\",\n \"product_id\": \"PROD-894495\",\n \"user_id\": \"0e93d4dc-0d39-4af2-8ec3-d8d1250011b9\",\n \"rating\": 4,\n \"title\": \"Great how data open such.\",\n \"content\": \"City not either situation all along might. Under could expect build member. Fish ready onto white majority.\",\n \"date\": \"2026-01-05\",\n \"verified_purchase\": false,\n \"helpful_votes\": 57\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-1521978</review_id>\n<product_id>PROD-894495</product_id>\n<user_id>0e93d4dc-0d39-4af2-8ec3-d8d1250011b9</user_id>\n<rating>4</rating>\n<title>Great how data open such.</title>\n<content>City not either situation all along might. Under could expect build member. Fish ready onto white majority.</content>\n<date>2026-01-05</date>\n<verified_purchase>False</verified_purchase>\n<helpful_votes>57</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 202
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output lab result as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id = \"LAB-8093004\"\npatient_mrn = \"MRN-777027\"\norder_date = \"2026-01-05\"\npanel = \"CMP\"\n[[results]]\ntest = \"Glucose\"\nvalue = 140.2\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 96.3\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 185.0\nunit = \"g/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 139.7\nunit = \"g/dL\"\nflag = \"low\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 169
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate clinical note data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nnote_id: CN-7937835\npatient:\n mrn: MRN-749785\n age: 66\n gender: M\nencounter_date: '2026-01-06'\nchief_complaint: chest pain\nvitals:\n bp: 179/85\n hr: 81\n temp_f: 101.7\nassessment:\n- problem: hypertension\n icd10: I52\n- problem: diabetes\n icd10: J76\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 140
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-8172649,Rachel Clark,\"Pattern capital time compare include night top. Large than important morning.\nCard authority protect\",Triple-buffered responsive model,2026-01-03T00:35:22.551008,Business,392,\"[\"\"consider\"\", \"\"whatever\"\", \"\"part\"\", \"\"however\"\", \"\"special\"\"]\",49705\r\nART-1645366,Amanda Martinez,\"Crime establish ahead program speech child. Contain reveal ahead fire capital necessary.\nSuggest tow\",Enterprise-wide reciprocal application,2026-01-01T21:09:16.034149,Business,1537,\"[\"\"season\"\", \"\"site\"\", \"\"political\"\", \"\"loss\"\", \"\"chair\"\"]\",98841\r\nART-5999482,Dennis Allen,\"Not way heart decision. Product seven into here girl argue. Free effect central everything white.\nPo\",Monitored 24/7 budgetary management,2026-01-05T03:19:57.275932,Politics,784,\"[\"\"mouth\"\", \"\"maintain\"\", \"\"establish\"\"]\",86058\r\nART-4000273,Austin Jones,Consider probably show when grow opportunity. Lay find relationship realize give. Ten if reflect mil,Assimilated asymmetric implementation,2026-01-06T00:27:11.144144,Tech,109,\"[\"\"benefit\"\", \"\"song\"\", \"\"vote\"\", \"\"long\"\", \"\"commercial\"\"]\",10210\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\narticle_id: ART-8172649\nheadline: Triple-buffered responsive model\nauthor: Rachel Clark\npublished: '2026-01-03T00:35:22.551008'\nsection: Business\ncontent: 'Pattern capital time compare include night top. Large than important morning.\n\n Card authority protect present return while middle. Development miss write five.'\ntags:\n- consider\n- whatever\n- part\n- however\n- special\nviews: 49705\nshares: 392\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 178
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<level>ERROR</level>\n<service>writeService</service>\n<error_id>85223c4c-4b76-4351-95ee-55a2460043f3</error_id>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"level\": \"ERROR\",\n \"service\": \"writeService\",\n \"error_id\": \"85223c4c-4b76-4351-95ee-55a2460043f3\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 105
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntitle: Stand-alone empowering functionalities 101\nschedule:\n- week: 1\n topic: class\n- week: 2\n topic: leave\n- week: 3\n topic: develop\n- week: 4\n topic: style\n- week: 5\n topic: again\n- week: 6\n topic: man\n- week: 7\n topic: list\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 150
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-469887\",\n \"is_available\": true,\n \"reviews\": 612,\n \"name\": \"Networked executive capability\",\n \"currency\": \"USD\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 114
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nGDK183,CRS-6873,3,40,30,30,Melinda Thompson,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"girl\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"explain\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"center\"\"}, {\"\"we\",Fall 2020,Grass-roots 24/7 emulation 101\r\nUWL437,CRS-9225,4,40,30,30,Monica Stewart,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"Democrat\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"clearly\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"sign\"\"}, {\"\"\",Fall 2024,Balanced interactive initiative 101\r\nRFE382,CRS-4501,4,40,30,30,Ryan Morris DDS,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"address\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"democratic\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"least\"\"},\",Fall 2023,Persistent next generation superstructure 101\r\nRLJ212,CRS-9484,4,40,30,30,Lisa Blevins,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"join\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"safe\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"we\"\"}, {\"\"week\"\": 4,\",Spring 2023,De-engineered transitional functionalities 101\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ncourse_id: CRS-6873\ncode: GDK183\ntitle: Grass-roots 24/7 emulation 101\ninstructor: Melinda Thompson\ncredits: 3\nterm: Fall 2020\nschedule:\n- week: 1\n topic: girl\n- week: 2\n topic: explain\n- week: 3\n topic: center\n- week: 4\n topic: almost\n- week: 5\n topic: property\n- week: 6\n topic: call\n- week: 7\n topic: bad\n- week: 8\n topic: study\n- week: 9\n topic: campaign\n- week: 10\n topic: performance\n- week: 11\n topic: sport\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 198
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"February 2020\",\n \"total_revenue\": 2007174,\n \"units_sold\": 24558,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 235807,\n \"growth\": 46.03\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 4419318,\n \"growth\": 24.35\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6554\",\n \"sales\": 258652\n },\n {\n \"sku\": \"SKU-8652\",\n \"sales\": 200091\n },\n {\n \"sku\": \"SKU-9581\",\n \"sales\": 65110\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 197
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"instructor\": \"Rachel Moreno DVM\",\n \"credits\": 4,\n \"course_id\": \"CRS-8305\",\n \"title\": \"Open-architected even-keeled support 101\",\n \"term\": \"Spring 2023\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<instructor>Rachel Moreno DVM</instructor>\n<credits>4</credits>\n<course_id>CRS-8305</course_id>\n<title>Open-architected even-keeled support 101</title>\n<term>Spring 2023</term>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 143
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output clinical note as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-8293808\",\n \"patient\": {\n \"mrn\": \"MRN-980604\",\n \"age\": 24,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-05\",\n \"chief_complaint\": \"fever\",\n \"vitals\": {\n \"bp\": \"150/98\",\n \"hr\": 93,\n \"temp_f\": 102.4\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J39\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 159
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id = \"CTR-896633\"\neffective_date = \"2026-01-03\"\nterm_months = 21\nvalue = 926875\nstatus = \"pending\"\n[[parties]]\nname = \"Smith-Cross\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Carrillo and Sons\"\nrole = \"party_b\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 127
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"contract_id\": \"CTR-370819\",\n \"parties\": [\n {\n \"name\": \"Stewart, Thompson and Rogers\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Jackson, Griffin and Flowers\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 13,\n \"value\": 109351,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-370819</contract_id>\n<parties>\n<name>Stewart, Thompson and Rogers</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Jackson, Griffin and Flowers</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-01</effective_date>\n<term_months>13</term_months>\n<value>109351</value>\n<status>active</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 173
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-3766387</note_id>\n<patient>\n<mrn>MRN-378219</mrn>\n<age>48</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>145/101</bp>\n<hr>106</hr>\n<temp_f>101.7</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>J94</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 179
}
|
generation_xml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-7328466\",\n \"patient_mrn\": \"MRN-740510\",\n \"prescriber\": \"William Hebert\",\n \"date\": \"2026-01-04\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"BID\",\n \"quantity\": 60\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-7328466</rx_id>\n<patient_mrn>MRN-740510</patient_mrn>\n<prescriber>William Hebert</prescriber>\n<date>2026-01-04</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>20mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Metformin</name>\n<dosage>20mg</dosage>\n<frequency>BID</frequency>\n<quantity>60</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 190
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"content\": \"Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\\nStrong who against entire.\\nKid television artist dream back agency. Need main ago investment job behavior.\",\n \"published\": \"2026-01-03T04:54:27.964292\",\n \"views\": 73181,\n \"headline\": \"Vision-oriented analyzing groupware\",\n \"section\": \"Business\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<content>Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\nStrong who against entire.\nKid television artist dream back agency. Need main ago investment job behavior.</content>\n<published>2026-01-03T04:54:27.964292</published>\n<views>73181</views>\n<headline>Vision-oriented analyzing groupware</headline>\n<section>Business</section>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 193
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the data below from YAML to TOML:\ndate: '2026-01-04'\nuser_id: d6e6e646-61a4-4af9-a9a1-d03d234244eb\ncontent: 'It herself scene five side support onto. Shake fear western believe. Say\n fact shoulder investment television pretty suffer.\n\n Ground listen official hand at indeed. Effort thus wife control.'\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from YAML to TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ndate = \"2026-01-04\"\nuser_id = \"d6e6e646-61a4-4af9-a9a1-d03d234244eb\"\ncontent = \"It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\\nGround listen official hand at indeed. Effort thus wife control.\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 144
}
|
conversion_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-9719971\",\n \"patient_mrn\": \"MRN-909141\",\n \"prescriber\": \"Heather Stephens\",\n \"date\": \"2026-01-05\",\n \"medications\": [\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-9719971</rx_id>\n<patient_mrn>MRN-909141</patient_mrn>\n<prescriber>Heather Stephens</prescriber>\n<date>2026-01-05</date>\n<medications>\n<name>Atorvastatin</name>\n<dosage>20mg</dosage>\n<frequency>daily</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 160
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<value>911148</value>\n<contract_id>CTR-919818</contract_id>\n<parties>\n<name>Riggs, Carey and Rojas</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Mcdowell-Koch</name>\n<role>party_b</role>\n</parties>\n<status>active</status>\n<term_months>18</term_months>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"value\": 911148,\n \"contract_id\": \"CTR-919818\",\n \"parties\": [\n {\n \"name\": \"Riggs, Carey and Rojas\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Mcdowell-Koch\",\n \"role\": \"party_b\"\n }\n ],\n \"status\": \"active\",\n \"term_months\": 18\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 143
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id: POST-86898750\nplatform: instagram\nuser_id: a47ec401-ca4e-44b5-afc7-6c2b372f589e\nusername: dylan00\ncontent: 'Might north politics.\n\n Moment bad without change physical store call. Enjoy question state student political\n boy tonight.\n\n Soon ten last small develop left enter. Health lead bank and air capital save.'\ntimestamp: '2026-01-07T13:51:25.591017'\nhashtags:\n- '#kid'\n- '#off'\n- '#school'\n- '#fund'\nengagement:\n likes: 9146\n shares: 205\n comments: 18\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 196
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate error log data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: fd278ff8-fdfc-4b1d-81ec-31cf5ce70502\ntimestamp: '2026-01-07T13:51:26.554266'\nlevel: ERROR\nservice: heartService\nmessage: Attack candidate in give wish tree.\nstack_trace:\n- at thousand.py:354\n- at forget.py:20\n- at consider.py:392\ncontext:\n user_id: d753ac0c-8931-4c37-8bd5-01413aaaba41\n request_id: b35b2bd7-dc59-4d80-ba5d-dc21fa7f0bf7\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 163
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntxn_id: TXN-59995807\ncustomer_id: 0d66cadd-c42f-4e9b-ae40-46d71f47623d\ntimestamp: '2026-01-07T13:51:27.084892'\nitems:\n- sku: SKU-83766\n qty: 4\n price: 55.35\n- sku: SKU-77209\n qty: 2\n price: 217.97\n- sku: SKU-11210\n qty: 5\n price: 436.04\nsubtotal: 1600.85\ntax: 34.84\ntotal: 602.79\npayment_method: apple_pay\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 157
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nitems:\n- sku: SKU-71565\n qty: 1\n price: 387.38\n- sku: SKU-23891\n qty: 1\n price: 432.74\n- sku: SKU-77840\n qty: 1\n price: 463.12\n- sku: SKU-27496\n qty: 3\n price: 295.3\ntax: 39.55\ntotal: 1865.58\ncustomer_id: bf96f80b-072c-4f04-82b0-c235c01681a8\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 142
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output lab result as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id: LAB-3793814\npatient_mrn: MRN-247204\norder_date: '2026-01-03'\npanel: CBC\nresults:\n- test: Hemoglobin\n value: 188.2\n unit: g/dL\n flag: low\n- test: WBC\n value: 197.7\n unit: mg/dL\n flag: high\n- test: Glucose\n value: 196.4\n unit: mg/dL\n flag: high\n- test: Glucose\n value: 193.9\n unit: g/dL\n flag: high\n- test: Glucose\n value: 197.2\n unit: g/dL\n flag: low\n- test: Hemoglobin\n value: 109.5\n unit: mg/dL\n flag: normal\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 186
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>September 2022</period>\n<total_revenue>4880286</total_revenue>\n<units_sold>74173</units_sold>\n<channels>\n<name>retail</name>\n<revenue>2000312</revenue>\n<growth>0.96</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>3751658</revenue>\n<growth>-3.19</growth>\n</channels>\n<top_products>\n<sku>SKU-6977</sku>\n<sales>264067</sales>\n</top_products>\n<top_products>\n<sku>SKU-7032</sku>\n<sales>443161</sales>\n</top_products>\n<top_products>\n<sku>SKU-1793</sku>\n<sales>209512</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nperiod: September 2022\ntotal_revenue: 4880286\nunits_sold: 74173\nchannels:\n- name: retail\n revenue: 2000312\n growth: 0.96\n- name: wholesale\n revenue: 3751658\n growth: -3.19\ntop_products:\n- sku: SKU-6977\n sales: 264067\n- sku: SKU-7032\n sales: 443161\n- sku: SKU-1793\n sales: 209512\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 150
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id = \"REV-7169946\"\nproduct_id = \"PROD-908355\"\nuser_id = \"109a43ce-0a9d-47ca-b5cc-5940dcb3a5c0\"\nrating = 3\ntitle = \"Suffer kid daughter race still baby.\"\ncontent = \"Young lot card leave book. Thank agency tree shake. Manage organization reduce from sort soldier.\\nRun rich marriage parent discover kitchen. Positive person baby list positive really range.\"\ndate = \"2026-01-05\"\nverified_purchase = true\nhelpful_votes = 3\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 180
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-9458448\",\n \"patient_mrn\": \"MRN-362998\",\n \"prescriber\": \"Courtney Hansen\",\n \"date\": \"2026-01-02\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-9458448</rx_id>\n<patient_mrn>MRN-362998</patient_mrn>\n<prescriber>Courtney Hansen</prescriber>\n<date>2026-01-02</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>10mg</dosage>\n<frequency>BID</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 159
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-685161</product_id>\n<name>Balanced demand-driven capacity</name>\n<category>clothing</category>\n<price>554.83</price>\n<currency>USD</currency>\n<stock>872</stock>\n<is_available>True</is_available>\n<rating>3.32</rating>\n<reviews>212</reviews>\n<specs>\n<weight_kg>39.83</weight_kg>\n<dimensions>86x88x63cm</dimensions>\n</specs>\n</product_listing>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"product_id\": \"PROD-685161\",\n \"name\": \"Balanced demand-driven capacity\",\n \"category\": \"clothing\",\n \"price\": 554.83,\n \"currency\": \"USD\",\n \"stock\": 872,\n \"is_available\": true,\n \"rating\": 3.32,\n \"reviews\": 212,\n \"specs\": {\n \"weight_kg\": 39.83,\n \"dimensions\": \"86x88x63cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 152
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate prescription data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-9442688\",\n \"patient_mrn\": \"MRN-277514\",\n \"prescriber\": \"Timothy Goodman\",\n \"date\": \"2026-01-04\",\n \"medications\": [\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"5mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 195
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<title>Exactly almost full new record save.</title>\n<date>2026-01-02</date>\n<product_id>PROD-922306</product_id>\n<content>Arrive much low will teach. By possible nature learn could. Act hot whole guy experience.\nIdentify world fight stock. Force fear soon. Author night think.</content>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"title\": \"Exactly almost full new record save.\",\n \"date\": \"2026-01-02\",\n \"product_id\": \"PROD-922306\",\n \"content\": \"Arrive much low will teach. By possible nature learn could. Act hot whole guy experience.\\nIdentify world fight stock. Force fear soon. Author night think.\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 150
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output social media post as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-46905875\"\nplatform = \"instagram\"\nuser_id = \"2079b341-d50b-4860-ba15-aa28bbe0f5b3\"\nusername = \"xhernandez\"\ncontent = \"Serious degree upon late.\\nPainting throughout direction indicate night. Political business voice street child. Across between ready. Majority red mission prepare state.\"\ntimestamp = \"2026-01-07T13:51:26.735117\"\nhashtags = [ \"#easy\", \"#miss\",]\n\n[engagement]\nlikes = 6808\nshares = 9\ncomments = 24\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 182
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"instructor\": \"Tamara Stark\",\n \"term\": \"Spring 2022\",\n \"code\": \"VMA483\",\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<instructor>Tamara Stark</instructor>\n<term>Spring 2022</term>\n<code>VMA483</code>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 140
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Snow, Shelton and Parsons\nticker: LYEH\nquarter: Q3 2022\nrevenue: 49988929\nexpenses: 3428077\nnet_income: 8543670\neps: 3.41\nmetrics:\n profit_margin: 11.21\n roe: 5.99\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 121
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate social media post data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-18209344\"\nplatform = \"facebook\"\nuser_id = \"8880ae5d-22ce-466e-ac5d-224201417b5e\"\nusername = \"xmcbride\"\ncontent = \"Determine live compare center as direction. Eye experience low wear. If south level.\\nWorry expect style camera. Scene majority pay voice television professor.\"\ntimestamp = \"2026-01-07T13:51:27.602464\"\nhashtags = [ \"#culture\", \"#whole\", \"#central\",]\n\n[engagement]\nlikes = 2214\nshares = 878\ncomments = 146\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 184
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output prescription as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-9001624\npatient_mrn: MRN-695608\nprescriber: Stephen Davis\ndate: '2026-01-05'\nmedications:\n- name: Lisinopril\n dosage: 20mg\n frequency: daily\n quantity: 90\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate clinical note data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-6952117\",\n \"patient\": {\n \"mrn\": \"MRN-227055\",\n \"age\": 50,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-03\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"146/78\",\n \"hr\": 63,\n \"temp_f\": 97.9\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J35\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"K44\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"I58\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 194
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate transaction record data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"txn_id\": \"TXN-13058367\",\n \"customer_id\": \"852e4544-1bd4-44f1-abf0-2ff01b4a4792\",\n \"timestamp\": \"2026-01-07T13:51:26.835091\",\n \"items\": [\n {\n \"sku\": \"SKU-47822\",\n \"qty\": 3,\n \"price\": 237.72\n },\n {\n \"sku\": \"SKU-38430\",\n \"qty\": 4,\n \"price\": 285.9\n },\n {\n \"sku\": \"SKU-22327\",\n \"qty\": 1,\n \"price\": 141.71\n }\n ],\n \"subtotal\": 408.33,\n \"tax\": 11.32,\n \"total\": 1142.29,\n \"payment_method\": \"paypal\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 195
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following TOML to YAML:\nerror_id = \"92d36993-19b1-4c19-9b64-8b4669c6636f\"\ntimestamp = \"2026-01-07T13:51:27.222487\"\nlevel = \"WARNING\"\nservice = \"voiceService\"\nmessage = \"Analysis beautiful attack blue eye.\"\nstack_trace = [ \"at well.py:163\", \"at will.py:421\", \"at run.py:384\", \"at TV.py:103\",]\n\n[context]\nuser_id = \"c92bcb8f-c109-47f8-aa13-b43737a1fc38\"\nrequest_id = \"f4cb6737-30c9-41ef-814b-34c3ec971deb\"\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from TOML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nerror_id: 92d36993-19b1-4c19-9b64-8b4669c6636f\ntimestamp: '2026-01-07T13:51:27.222487'\nlevel: WARNING\nservice: voiceService\nmessage: Analysis beautiful attack blue eye.\nstack_trace:\n- at well.py:163\n- at will.py:421\n- at run.py:384\n- at TV.py:103\ncontext:\n user_id: c92bcb8f-c109-47f8-aa13-b43737a1fc38\n request_id: f4cb6737-30c9-41ef-814b-34c3ec971deb\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 166
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"June 2021\",\n \"total_revenue\": 1467254,\n \"units_sold\": 63744,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 2975287,\n \"growth\": -1.88\n },\n {\n \"name\": \"online\",\n \"revenue\": 2665464,\n \"growth\": 14.77\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-1172\",\n \"sales\": 348860\n },\n {\n \"sku\": \"SKU-4431\",\n \"sales\": 479568\n },\n {\n \"sku\": \"SKU-6244\",\n \"sales\": 245719\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate financial report data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Smith-Glover\nticker: JROI\nquarter: Q3 2023\nrevenue: 95238846\nexpenses: 30652579\nnet_income: 5856951\neps: 7.31\nmetrics:\n profit_margin: 9.94\n roe: 10.91\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 118
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-6224145</note_id>\n<patient>\n<mrn>MRN-560569</mrn>\n<age>88</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>119/73</bp>\n<hr>63</hr>\n<temp_f>100.0</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>I32</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 180
}
|
generation_xml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output customer review as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id = \"REV-1369973\"\nproduct_id = \"PROD-861575\"\nuser_id = \"a55bb48c-5dcb-464a-b952-9d377a4cb9c4\"\nrating = 1\ntitle = \"Relationship job find one allow law through.\"\ncontent = \"Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land.\"\ndate = \"2026-01-02\"\nverified_purchase = true\nhelpful_votes = 8\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 172
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"rating\": 4.54,\n \"stock\": 843,\n \"specs\": {\n \"weight_kg\": 34.7,\n \"dimensions\": \"61x86x65cm\"\n },\n \"currency\": \"USD\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<rating>4.54</rating>\n<stock>843</stock>\n<specs>\n<weight_kg>34.7</weight_kg>\n<dimensions>61x86x65cm</dimensions>\n</specs>\n<currency>USD</currency>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 135
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"contract_id\": \"CTR-313579\",\n \"parties\": [\n {\n \"name\": \"Roberts, Newton and Ortiz\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Garcia PLC\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 55,\n \"value\": 108642,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-313579</contract_id>\n<parties>\n<name>Roberts, Newton and Ortiz</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Garcia PLC</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-01</effective_date>\n<term_months>55</term_months>\n<value>108642</value>\n<status>active</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 168
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate prescription data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-9036427\npatient_mrn: MRN-461250\nprescriber: Zachary Berry\ndate: '2026-01-01'\nmedications:\n- name: Atorvastatin\n dosage: 5mg\n frequency: daily\n quantity: 30\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate prescription data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-5523111\"\ndate = \"2026-01-01\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"10mg\"\nfrequency = \"BID\"\nquantity = 60\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 106
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 6b141850-4372-44c1-8cf7-fc47780a5017\ntimestamp: '2026-01-07T13:51:26.727039'\nlevel: WARNING\nservice: fullService\nmessage: Simply human maintain sport.\nstack_trace:\n- at environmental.py:351\n- at develop.py:28\n- at send.py:431\ncontext:\n user_id: fad7b695-3fb8-4313-ad8d-c2b1d4034196\n request_id: 2ca5c81e-d6c8-42a4-9e09-9715e928fe91\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 162
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"error_id\": \"91d16731-5e7b-4a47-8285-7a54d79d3b76\",\n \"timestamp\": \"2026-01-07T13:51:25.635487\",\n \"level\": \"WARNING\",\n \"service\": \"AmericanService\",\n \"message\": \"Drug sell certainly major total.\",\n \"stack_trace\": [\n \"at although.py:151\",\n \"at mission.py:443\"\n ],\n \"context\": {\n \"user_id\": \"11d85442-7276-4e30-9249-06df8089bd39\",\n \"request_id\": \"f3cc0b9c-f4db-4c9d-bea8-f49774b1a7e6\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 179
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"May 2020\",\n \"total_revenue\": 9864225,\n \"units_sold\": 74086,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 906832,\n \"growth\": -8.93\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 2437365,\n \"growth\": 2.73\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-7032\",\n \"sales\": 420063\n },\n {\n \"sku\": \"SKU-9360\",\n \"sales\": 149398\n },\n {\n \"sku\": \"SKU-9440\",\n \"sales\": 105905\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-7122533</review_id>\n<content>Expert difficult hot radio mission. Throw southern he book way media particular.</content>\n<rating>1</rating>\n<date>2026-01-06</date>\n<verified_purchase>False</verified_purchase>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-7122533\",\n \"content\": \"Expert difficult hot radio mission. Throw southern he book way media particular.\",\n \"rating\": 1,\n \"date\": \"2026-01-06\",\n \"verified_purchase\": false\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 129
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate = \"2026-01-04\"\nuser_id = \"d6e6e646-61a4-4af9-a9a1-d03d234244eb\"\ncontent = \"It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\\nGround listen official hand at indeed. Effort thus wife control.\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 143
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"March 2022\",\n \"total_revenue\": 6503980,\n \"units_sold\": 7670,\n \"channels\": [\n {\n \"name\": \"retail\",\n \"revenue\": 3279241,\n \"growth\": 22.76\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 1469640,\n \"growth\": 16.07\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-8081\",\n \"sales\": 71747\n },\n {\n \"sku\": \"SKU-8211\",\n \"sales\": 475825\n },\n {\n \"sku\": \"SKU-4565\",\n \"sales\": 485553\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate prescription data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate = \"2026-01-06\"\npatient_mrn = \"MRN-259808\"\nrx_id = \"RX-8539167\"\nprescriber = \"Joseph Griffin\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"10mg\"\nfrequency = \"daily\"\nquantity = 90\n\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"10mg\"\nfrequency = \"TID\"\nquantity = 30\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 30\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 163
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id: ART-8221745\nheadline: Polarized zero administration support\nauthor: Maria Johnson\npublished: '2026-01-03T08:37:58.870132'\nsection: Business\ncontent: 'Would movement white military what them cup. Available remember control\n staff. None mean hundred PM.\n\n Improve wear produce price according. He method market computer TV strategy.\n\n Body into language. Which other hear they look some option.'\ntags:\n- environment\n- name\n- receive\n- happen\n- join\nviews: 46852\nshares: 763\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 199
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate contract data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-457828</contract_id>\n<effective_date>2026-01-01</effective_date>\n<term_months>32</term_months>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 120
}
|
generation_xml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-3305496\"\npatient_mrn = \"MRN-551064\"\nprescriber = \"Eric Jackson\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"20mg\"\nfrequency = \"daily\"\nquantity = 90\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\nOrtega-Owens,1.51,44591506,5.54,6.32,3197580,Q3 2022,37598920,YLLB\r\nWhite-Olson,7.4,43583851,20.88,6.11,15633315,Q2 2021,7675359,QPRL\r\n\"Obrien, Stafford and Johnson\",3.17,27196822,21.87,10.54,7469164,Q4 2024,79145487,TUNG\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 156
}
|
generation_csv
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"value\": 911148,\n \"contract_id\": \"CTR-919818\",\n \"parties\": [\n {\n \"name\": \"Riggs, Carey and Rojas\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Mcdowell-Koch\",\n \"role\": \"party_b\"\n }\n ],\n \"status\": \"active\",\n \"term_months\": 18\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 142
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-942707\",\n \"name\": \"Organic demand-driven installation\",\n \"category\": \"books\",\n \"price\": 698.66,\n \"currency\": \"USD\",\n \"stock\": 819,\n \"is_available\": true,\n \"rating\": 4.45,\n \"reviews\": 103,\n \"specs\": {\n \"weight_kg\": 32.63,\n \"dimensions\": \"66x30x83cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 151
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output contract as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id: CTR-299234\nparties:\n- name: Murphy, Hawkins and Mckenzie\n role: party_a\n- name: Collins-Miller\n role: party_b\neffective_date: '2026-01-06'\nterm_months: 46\nvalue: 506357\nstatus: pending\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 126
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"level\": \"ERROR\",\n \"service\": \"writeService\",\n \"error_id\": \"85223c4c-4b76-4351-95ee-55a2460043f3\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<level>ERROR</level>\n<service>writeService</service>\n<error_id>85223c4c-4b76-4351-95ee-55a2460043f3</error_id>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 122
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output financial report as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\nTaylor Ltd,1.63,52626087,23.4,21.22,18580243,Q1 2024,69752271,AOED\r\n\"Berg, Edwards and Washington\",2.64,21304251,24.59,21.54,15746169,Q4 2022,1384082,IKVG\r\nLopez Group,9.45,39741607,22.5,19.87,16715861,Q3 2024,12652451,YMDT\r\nSantana Group,1.95,7640424,11.86,13.46,5440388,Q4 2023,6451824,POVS\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 173
}
|
generation_csv
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f</error_id>\n<timestamp>2026-01-07T13:51:25.611338</timestamp>\n<level>ERROR</level>\n<service>typeService</service>\n<message>Suggest involve part skill write left participant.</message>\n<stack_trace>at risk.py:441</stack_trace>\n<stack_trace>at strategy.py:390</stack_trace>\n<stack_trace>at performance.py:267</stack_trace>\n<stack_trace>at kind.py:265</stack_trace>\n<context>\n<user_id>3651fff2-dc6a-4fe5-a964-ed26913f3e4b</user_id>\n<request_id>f4fc48f0-6374-4e80-b666-89c2abac0904</request_id>\n</context>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"error_id\": \"2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f\",\n \"timestamp\": \"2026-01-07T13:51:25.611338\",\n \"level\": \"ERROR\",\n \"service\": \"typeService\",\n \"message\": \"Suggest involve part skill write left participant.\",\n \"stack_trace\": [\n \"at risk.py:441\",\n \"at strategy.py:390\",\n \"at performance.py:267\",\n \"at kind.py:265\"\n ],\n \"context\": {\n \"user_id\": \"3651fff2-dc6a-4fe5-a964-ed26913f3e4b\",\n \"request_id\": \"f4fc48f0-6374-4e80-b666-89c2abac0904\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 195
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nmessage: Baby inside high our should character study quickly.\nstack_trace:\n- at standard.py:486\n- at memory.py:53\n- at team.py:342\ncontext:\n user_id: b89e754b-fd03-47c7-9600-09a7cb6d3517\n request_id: 0aea7b7e-f431-4209-a4db-008320d27043\ntimestamp: '2026-01-07T13:51:25.507604'\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 147
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-299234</contract_id>\n<parties>\n<name>Murphy, Hawkins and Mckenzie</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Collins-Miller</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-06</effective_date>\n<term_months>46</term_months>\n<value>506357</value>\n<status>pending</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 169
}
|
generation_xml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate social media post data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-49469407\"\nplatform = \"instagram\"\nuser_id = \"c776cd7c-2538-4c81-83c8-03afd724bed1\"\nusername = \"donald18\"\ncontent = \"Knowledge between friend wife property kid out. Trouble recent member sort arrive foot space good.\"\ntimestamp = \"2026-01-07T13:51:26.031233\"\nhashtags = [ \"#daughter\", \"#after\", \"#affect\", \"#goal\",]\n\n[engagement]\nlikes = 2564\nshares = 187\ncomments = 95\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 170
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"specs\": {\n \"weight_kg\": 41.33,\n \"dimensions\": \"19x24x69cm\"\n },\n \"price\": 743.81,\n \"is_available\": true,\n \"rating\": 2.69,\n \"stock\": 485\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 117
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"contract_id\": \"CTR-274282\",\n \"parties\": [\n {\n \"name\": \"Schroeder LLC\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Kemp-Jones\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 28,\n \"value\": 285721,\n \"status\": \"active\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 146
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate sales analytics data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nperiod: September 2024\ntotal_revenue: 6726526\nunits_sold: 45392\nchannels:\n- name: retail\n revenue: 2051641\n growth: 15.93\n- name: wholesale\n revenue: 4340607\n growth: -6.59\ntop_products:\n- sku: SKU-7798\n sales: 367269\n- sku: SKU-2105\n sales: 291023\n- sku: SKU-5730\n sales: 275348\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 149
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate transaction record data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"customer_id\": \"5642be10-2f96-4bf3-93bb-ea73b498db7e\",\n \"timestamp\": \"2026-01-07T13:51:27.704310\",\n \"total\": 2159.3,\n \"tax\": 150.65,\n \"items\": [\n {\n \"sku\": \"SKU-21107\",\n \"qty\": 2,\n \"price\": 436.86\n },\n {\n \"sku\": \"SKU-34269\",\n \"qty\": 3,\n \"price\": 260.71\n },\n {\n \"sku\": \"SKU-81249\",\n \"qty\": 3,\n \"price\": 416.92\n },\n {\n \"sku\": \"SKU-97216\",\n \"qty\": 3,\n \"price\": 177.96\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 196
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output transaction record as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntxn_id: TXN-60159725\ncustomer_id: 13707a49-23b0-4133-8216-7e83986c9575\ntimestamp: '2026-01-07T13:51:27.689251'\nitems:\n- sku: SKU-82899\n qty: 5\n price: 298.29\n- sku: SKU-51515\n qty: 4\n price: 343.78\n- sku: SKU-53336\n qty: 3\n price: 488.21\n- sku: SKU-52517\n qty: 2\n price: 291.79\nsubtotal: 1914.1\ntax: 175.88\ntotal: 1360.6\npayment_method: credit_card\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 168
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>January 2022</period>\n<total_revenue>7456708</total_revenue>\n<units_sold>82349</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>3622404</revenue>\n<growth>-8.05</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>1893923</revenue>\n<growth>2.21</growth>\n</channels>\n<top_products>\n<sku>SKU-2073</sku>\n<sales>98550</sales>\n</top_products>\n<top_products>\n<sku>SKU-3707</sku>\n<sales>233488</sales>\n</top_products>\n<top_products>\n<sku>SKU-7843</sku>\n<sales>172526</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"period\": \"January 2022\",\n \"total_revenue\": 7456708,\n \"units_sold\": 82349,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 3622404,\n \"growth\": -8.05\n },\n {\n \"name\": \"online\",\n \"revenue\": 1893923,\n \"growth\": 2.21\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-2073\",\n \"sales\": 98550\n },\n {\n \"sku\": \"SKU-3707\",\n \"sales\": 233488\n },\n {\n \"sku\": \"SKU-7843\",\n \"sales\": 172526\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 198
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-5911912</review_id>\n<product_id>PROD-652506</product_id>\n<user_id>e81c58cf-1a13-4302-a93a-5e1fbbfd28db</user_id>\n<rating>3</rating>\n<title>Their husband whole president threat argue.</title>\n<content>Happen member step can deal animal fine. Like among study from book.\nDemocratic significant every sport next want. List religious computer rise wrong.</content>\n<date>2026-01-02</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>61</helpful_votes>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-5911912\",\n \"product_id\": \"PROD-652506\",\n \"user_id\": \"e81c58cf-1a13-4302-a93a-5e1fbbfd28db\",\n \"rating\": 3,\n \"title\": \"Their husband whole president threat argue.\",\n \"content\": \"Happen member step can deal animal fine. Like among study from book.\\nDemocratic significant every sport next want. List religious computer rise wrong.\",\n \"date\": \"2026-01-02\",\n \"verified_purchase\": true,\n \"helpful_votes\": 61\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 187
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Hill-Marsh\nticker: ZFVR\nquarter: Q3 2024\nrevenue: 46703834\nexpenses: 77071880\nnet_income: 4141173\neps: 8.71\nmetrics:\n profit_margin: 28.84\n roe: 14.06\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 119
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 03dcbba2-8070-483e-a807-51e4c6301bf5\ntimestamp: '2026-01-07T13:51:27.875594'\nlevel: WARNING\nservice: stockService\nmessage: Feel garden dark.\nstack_trace:\n- at another.py:304\n- at happy.py:331\n- at record.py:415\ncontext:\n user_id: cedcf075-a01b-42e9-acdc-a300ea843992\n request_id: acbfd7fd-a4ab-431b-a098-ac4537826f14\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 159
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nbooks,USD,True,Decentralized heuristic migration,124.58,PROD-791864,3.59,538,30x16x25cm,9.83,601\r\nclothing,USD,True,Future-proofed systematic hardware,992.92,PROD-537096,4.54,344,18x72x25cm,5.0,464\r\nclothing,USD,True,Reduced multimedia framework,219.85,PROD-359731,4.05,390,77x18x94cm,47.87,513\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 178
}
|
generation_csv
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\ncontent,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username\r\nUse Mr only week. Crime form attention. Right world stand surface rate three.,4,9998,653,\"[\"\"#economic\"\", \"\"#speak\"\"]\",instagram,POST-64636774,2026-01-07T13:51:26.942814,180a1898-015f-483f-94a7-e771a6fb148e,melissa16\r\nMaybe wish bit allow share. Reduce student sure eat thing charge particular. Each factor trouble val,247,217,964,\"[\"\"#so\"\", \"\"#soon\"\", \"\"#their\"\", \"\"#ready\"\"]\",instagram,POST-72911154,2026-01-07T13:51:26.945630,1981183e-f73f-4c00-ab72-cbf1d7ecf731,reginatorres\r\n\"Son education require. Nor military relate paper. Field technology crime everyone write.\nBetween wil\",257,1206,949,\"[\"\"#raise\"\", \"\"#indeed\"\", \"\"#one\"\", \"\"#tonight\"\"]\",facebook,POST-35525154,2026-01-07T13:51:26.946054,b98f51d8-23b8-416c-a8b8-6dcfc723dc1a,stephen38\r\n\"Must laugh money be. Community day real.\nExpert writer reach simply seem party.\nInvolve person socie\",271,1283,925,\"[\"\"#character\"\", \"\"#and\"\"]\",facebook,POST-19696784,2026-01-07T13:51:26.946507,eec1b96a-3937-464c-a8d8-af73cf0653bd,lkline\r\n\"Foreign thus not though. Relate mouth usually ball risk. Shoulder sure someone either.\nPerform charg\",490,7715,362,\"[\"\"#so\"\", \"\"#particularly\"\"]\",facebook,POST-23301440,2026-01-07T13:51:26.946842,6a103282-d9f4-48b3-9a9b-bd61f3001063,znguyen\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from CSV to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\npost_id: POST-64636774\nplatform: instagram\nuser_id: 180a1898-015f-483f-94a7-e771a6fb148e\nusername: melissa16\ncontent: Use Mr only week. Crime form attention. Right world stand surface rate three.\ntimestamp: '2026-01-07T13:51:26.942814'\nhashtags:\n- '#economic'\n- '#speak'\nengagement:\n likes: 9998\n shares: 653\n comments: 4\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 161
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id: EXP-330074\ntitle: Effect of politics on stop\nmethodology:\n design: RCT\n sample_size: 328\n duration_days: 247\nresults:\n- metric: efficacy\n baseline: 34.54\n endpoint: 53.32\n p_value: 0.0487\n- metric: safety\n baseline: 10.4\n endpoint: 13.84\n p_value: 0.1164\n- metric: efficacy\n baseline: 78.27\n endpoint: 47.78\n p_value: 0.0781\nconclusion: non-significant\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 173
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this JSON data into YAML format:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Assimilated neutral archive API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/sea\": {\n \"get\": {\n \"summary\": \"Team happen challenge address expert manage beyond\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nopenapi: 3.0.0\ninfo:\n title: Assimilated neutral archive API\n version: 1.0.0\npaths:\n /sea:\n get:\n summary: Team happen challenge address expert manage beyond\n parameters:\n - name: param0\n in: query\n type: string\n - name: param1\n in: query\n type: string\n - name: param2\n in: query\n type: string\n responses:\n '200':\n description: Success\n '400':\n description: Bad Request\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 199
}
|
conversion_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>e01a43f8-d4eb-4ec7-a325-ad2b31726d0f</error_id>\n<timestamp>2026-01-07T13:51:25.462522</timestamp>\n<level>ERROR</level>\n<service>winService</service>\n<message>Western energy project push building.</message>\n<stack_trace>at could.py:42</stack_trace>\n<stack_trace>at seem.py:198</stack_trace>\n<context>\n<user_id>7197800d-0acd-4eee-b9ab-24b5158dfa0a</user_id>\n<request_id>00c4c00d-dc22-4013-8495-1ed2381fc937</request_id>\n</context>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"error_id\": \"e01a43f8-d4eb-4ec7-a325-ad2b31726d0f\",\n \"timestamp\": \"2026-01-07T13:51:25.462522\",\n \"level\": \"ERROR\",\n \"service\": \"winService\",\n \"message\": \"Western energy project push building.\",\n \"stack_trace\": [\n \"at could.py:42\",\n \"at seem.py:198\"\n ],\n \"context\": {\n \"user_id\": \"7197800d-0acd-4eee-b9ab-24b5158dfa0a\",\n \"request_id\": \"00c4c00d-dc22-4013-8495-1ed2381fc937\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 178
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate contract data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"term_months\": 33,\n \"parties\": [\n {\n \"name\": \"Hart-Villanueva\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Roberts Ltd\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-05\",\n \"value\": 95653\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 134
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output api specification as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Object-based multimedia secured line API\"\nversion = \"1.0.0\"\n\n[paths.\"/party\".get]\nsummary = \"Discussion partner stay wear again.\"\n[[paths.\"/party\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/party\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/party\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/party\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 188
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nelectronics,USD,True,Function-based dedicated installation,364.53,PROD-738287,1.64,854,48x33x88cm,19.72,956\r\nelectronics,USD,True,Quality-focused holistic forecast,453.49,PROD-220410,3.4,204,71x68x73cm,22.05,907\r\nelectronics,USD,True,Synchronized high-level implementation,551.15,PROD-194348,2.7,28,21x96x93cm,12.15,925\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 184
}
|
generation_csv
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>03dcbba2-8070-483e-a807-51e4c6301bf5</error_id>\n<timestamp>2026-01-07T13:51:27.875594</timestamp>\n<level>WARNING</level>\n<service>stockService</service>\n<message>Feel garden dark.</message>\n<stack_trace>at another.py:304</stack_trace>\n<stack_trace>at happy.py:331</stack_trace>\n<stack_trace>at record.py:415</stack_trace>\n<context>\n<user_id>cedcf075-a01b-42e9-acdc-a300ea843992</user_id>\n<request_id>acbfd7fd-a4ab-431b-a098-ac4537826f14</request_id>\n</context>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"error_id\": \"03dcbba2-8070-483e-a807-51e4c6301bf5\",\n \"timestamp\": \"2026-01-07T13:51:27.875594\",\n \"level\": \"WARNING\",\n \"service\": \"stockService\",\n \"message\": \"Feel garden dark.\",\n \"stack_trace\": [\n \"at another.py:304\",\n \"at happy.py:331\",\n \"at record.py:415\"\n ],\n \"context\": {\n \"user_id\": \"cedcf075-a01b-42e9-acdc-a300ea843992\",\n \"request_id\": \"acbfd7fd-a4ab-431b-a098-ac4537826f14\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 181
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from CSV to JSON:\ncategory,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase\r\n,Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Moder,,2026-01-02,8,,,,PROD-861575,1,REV-1369973,,,,,Relationship job find one allow law through.,a55bb48c-5dcb-464a-b952-9d377a4cb9c4,True\r\nelectronics,,USD,,,True,Synergistic regional success,90.86,PROD-274336,2.93,,602,23x29x34cm,41.78,989,,,\r\nclothing,,USD,,,True,Synchronized bandwidth-monitored database,891.71,PROD-686329,4.85,,277,82x52x99cm,46.05,538,,,\r\nbooks,,USD,,,True,Sharable 24/7 Graphic Interface,180.34,PROD-508713,2.29,,602,43x66x90cm,47.52,362,,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from CSV to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-1369973\",\n \"product_id\": \"PROD-861575\",\n \"user_id\": \"a55bb48c-5dcb-464a-b952-9d377a4cb9c4\",\n \"rating\": 1,\n \"title\": \"Relationship job find one allow law through.\",\n \"content\": \"Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land.\",\n \"date\": \"2026-01-02\",\n \"verified_purchase\": true,\n \"helpful_votes\": 8\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 186
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nnote_id = \"CN-8293808\"\nencounter_date = \"2026-01-05\"\nchief_complaint = \"fever\"\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"J39\"\n\n[patient]\nmrn = \"MRN-980604\"\nage = 24\ngender = \"F\"\n\n[vitals]\nbp = \"150/98\"\nhr = 93\ntemp_f = 102.4\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 130
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output sales analytics as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nperiod = \"February 2022\"\ntotal_revenue = 6033804\nunits_sold = 27183\n[[channels]]\nname = \"wholesale\"\nrevenue = 4147239\ngrowth = 40.37\n\n[[channels]]\nname = \"online\"\nrevenue = 2663137\ngrowth = 9.96\n\n[[top_products]]\nsku = \"SKU-2538\"\nsales = 420940\n\n[[top_products]]\nsku = \"SKU-8680\"\nsales = 364206\n\n[[top_products]]\nsku = \"SKU-2062\"\nsales = 350623\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 161
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"rx_id\": \"RX-5160762\",\n \"patient_mrn\": \"MRN-568012\",\n \"prescriber\": \"Linda Gonzalez\",\n \"date\": \"2026-01-06\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"daily\",\n \"quantity\": 60\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-5160762</rx_id>\n<patient_mrn>MRN-568012</patient_mrn>\n<prescriber>Linda Gonzalez</prescriber>\n<date>2026-01-06</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>20mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Atorvastatin</name>\n<dosage>5mg</dosage>\n<frequency>daily</frequency>\n<quantity>60</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 191
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id: EXP-139463\ntitle: Effect of quite on arm\nmethodology:\n design: RCT\n sample_size: 371\n duration_days: 284\nresults:\n- metric: safety\n baseline: 91.61\n endpoint: 76.9\n p_value: 0.4003\n- metric: safety\n baseline: 58.96\n endpoint: 23.83\n p_value: 0.3437\n- metric: safety\n baseline: 23.31\n endpoint: 88.63\n p_value: 0.3018\nconclusion: non-significant\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 171
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-168652</experiment_id>\n<title>Effect of green on from</title>\n<methodology>\n<design>cohort</design>\n<sample_size>797</sample_size>\n<duration_days>186</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>24.16</baseline>\n<endpoint>44.82</endpoint>\n<p_value>0.0559</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>16.54</baseline>\n<endpoint>28.48</endpoint>\n<p_value>0.2997</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"experiment_id\": \"EXP-168652\",\n \"title\": \"Effect of green on from\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 797,\n \"duration_days\": 186\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 24.16,\n \"endpoint\": 44.82,\n \"p_value\": 0.0559\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 16.54,\n \"endpoint\": 28.48,\n \"p_value\": 0.2997\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 192
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"date\": \"2026-01-06\",\n \"patient_mrn\": \"MRN-259808\",\n \"rx_id\": \"RX-8539167\",\n \"prescriber\": \"Joseph Griffin\",\n \"medications\": [\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"daily\",\n \"quantity\": 90\n },\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 197
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate customer review data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id: REV-4235678\nproduct_id: PROD-754494\nuser_id: 29638f7d-f697-4ae7-8fde-a1a70bcd6476\nrating: 5\ntitle: Help program law water necessary return clearly.\ncontent: Team hold course throw center open enjoy old. Huge candidate still act decade\n civil. Safe middle indeed.\ndate: '2026-01-03'\nverified_purchase: false\nhelpful_votes: 98\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 162
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from TOML to JSON:\nerror_id = \"c6e14566-270a-4a5f-a250-5239ca9174ac\"\ntimestamp = \"2026-01-07T13:51:26.338486\"\nlevel = \"ERROR\"\nservice = \"humanService\"\nmessage = \"Fear she east talk better central.\"\nstack_trace = [ \"at college.py:218\", \"at economy.py:209\", \"at let.py:252\", \"at whole.py:18\",]\n\n[context]\nuser_id = \"bda2bdb3-cc4e-4711-8927-aa42dc72d462\"\nrequest_id = \"c7d51186-07ee-4743-a193-c5688ac0d6c5\"\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from TOML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"error_id\": \"c6e14566-270a-4a5f-a250-5239ca9174ac\",\n \"timestamp\": \"2026-01-07T13:51:26.338486\",\n \"level\": \"ERROR\",\n \"service\": \"humanService\",\n \"message\": \"Fear she east talk better central.\",\n \"stack_trace\": [\n \"at college.py:218\",\n \"at economy.py:209\",\n \"at let.py:252\",\n \"at whole.py:18\"\n ],\n \"context\": {\n \"user_id\": \"bda2bdb3-cc4e-4711-8927-aa42dc72d462\",\n \"request_id\": \"c7d51186-07ee-4743-a193-c5688ac0d6c5\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 190
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<reviews>730</reviews>\n<category>books</category>\n<stock>824</stock>\n<is_available>True</is_available>\n<specs>\n<weight_kg>7.36</weight_kg>\n<dimensions>46x21x76cm</dimensions>\n</specs>\n</product_listing>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"reviews\": 730,\n \"category\": \"books\",\n \"stock\": 824,\n \"is_available\": true,\n \"specs\": {\n \"weight_kg\": 7.36,\n \"dimensions\": \"46x21x76cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 119
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-1995080\",\n \"patient_mrn\": \"MRN-674224\",\n \"prescriber\": \"Emily Herrera\",\n \"date\": \"2026-01-05\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"BID\",\n \"quantity\": 60\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 140
}
|
generation_json
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 234c0781-6e40-4e46-8b0d-ad1b39309eb0\ntimestamp: '2026-01-07T13:51:25.659911'\nlevel: WARNING\nservice: beyondService\nmessage: Section material entire top community.\nstack_trace:\n- at reason.py:320\n- at always.py:365\n- at red.py:27\ncontext:\n user_id: 6765bd92-f82e-426f-a383-fa0a088a0752\n request_id: 4ccfb0b5-8185-4d26-902a-0379b3534400\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 163
}
|
generation_yaml
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id = \"249c5a8d-effc-4f5a-9a18-79860cd86eba\"\ntimestamp = \"2026-01-07T13:51:25.844189\"\nlevel = \"CRITICAL\"\nservice = \"createService\"\nmessage = \"Capital carry as agree member lead one.\"\nstack_trace = [ \"at sign.py:359\", \"at college.py:115\", \"at try.py:133\",]\n\n[context]\nuser_id = \"e110a198-5d8a-4242-b2e4-6ec6ae49ca80\"\nrequest_id = \"939e8b37-2ce6-4ba0-bde6-ca285c8d396c\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 166
}
|
generation_toml
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-760727</contract_id>\n<parties>\n<name>King, Moore and Vazquez</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Brown, Henry and Craig</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-04</effective_date>\n<term_months>15</term_months>\n<value>170545</value>\n<status>active</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"contract_id\": \"CTR-760727\",\n \"parties\": [\n {\n \"name\": \"King, Moore and Vazquez\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Brown, Henry and Craig\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-04\",\n \"term_months\": 15,\n \"value\": 170545,\n \"status\": \"active\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 153
}
|
conversion_json
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"note_id\": \"CN-4036732\",\n \"patient\": {\n \"mrn\": \"MRN-366942\",\n \"age\": 79,\n \"gender\": \"M\"\n },\n \"encounter_date\": \"2026-01-06\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"102/96\",\n \"hr\": 61,\n \"temp_f\": 97.1\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"K52\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-4036732</note_id>\n<patient>\n<mrn>MRN-366942</mrn>\n<age>79</age>\n<gender>M</gender>\n</patient>\n<encounter_date>2026-01-06</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>102/96</bp>\n<hr>61</hr>\n<temp_f>97.1</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>K52</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 181
}
|
conversion_xml
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Convert the following XML to CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<vitals>\n<bp>131/104</bp>\n<hr>84</hr>\n<temp_f>99.9</temp_f>\n</vitals>\n<note_id>CN-3823498</note_id>\n<encounter_date>2026-01-06</encounter_date>\n</clinical_note>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from XML to CSV\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n,,2026-01-06,CN-3823498,,,,131/104,84,99.9\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K48\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K13\"\"}]\",fever,2026-01-06,CN-5143623,45,F,MRN-821610,174/60,79,100.2\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I34\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K71\"\"}]\",fever,2026-01-04,CN-4602383,58,F,MRN-126591,156/110,79,98.7\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 204
}
|
conversion_csv
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.