messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output product listing as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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:\nproduct_id = \"PROD-888613\"\nname = \"Multi-lateral attitude-oriented intranet\"\ncategory = \"electronics\"\nprice = 967.86\ncurrency = \"USD\"\nstock = 776\nis_available = true\nrating = 4.69\nreviews = 546\n\n[specs]\nweight_kg = 5.82\ndimensions = \"66x50x71cm\"\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 136
} |
[
{
"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 \"product_id\": \"PROD-877409\",\n \"name\": \"Decentralized mobile framework\",\n \"category\": \"electronics\",\n \"price\": 654.79,\n \"currency\": \"USD\",\n \"stock\": 219,\n \"is_available\": true,\n \"rating\": 3.88,\n \"reviews\": 74,\n \"specs\": {\n \"weight_kg\": 22.25,\n \"dimensions\": \"82x76x89cm\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from JSON 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:\nproduct_id: PROD-877409\nname: Decentralized mobile framework\ncategory: electronics\nprice: 654.79\ncurrency: USD\nstock: 219\nis_available: true\nrating: 3.88\nreviews: 74\nspecs:\n weight_kg: 22.25\n dimensions: 82x76x89cm\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 134
} |
[
{
"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: 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:\nrx_id = \"RX-7762492\"\npatient_mrn = \"MRN-190646\"\nprescriber = \"Laura Taylor\"\ndate = \"2026-01-04\"\n[[medications]]\nname = \"Metformin\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 30\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 118
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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<customer_review>\n<review_id>REV-8045456</review_id>\n<product_id>PROD-463913</product_id>\n<user_id>ba642a1e-c9a9-4bbb-9297-90eddc75d10f</user_id>\n<rating>4</rating>\n<title>Per responsibility past green trip.</title>\n<content>You woman when. Night collection whole officer along skin.\nExample against need. Likely you good effort. Billion design trouble special tree less tonight.</content>\n<date>2026-01-05</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>48</helpful_votes>\n</customer_review>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 215
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/response_get_parameters,paths_/response_get_responses_200_description,paths_/response_get_responses_400_description,paths_/response_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Realigned context-sensitive collaboration API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}]\",Success,Bad Request,Teacher our themselves author.,,,,\r\nGood news could well less plan. Two performance amount ability.,\"[{\"\"name\"\": \"\"Daniel Perez\"\", \"\"affiliation\"\": \"\"Wilson, Swanson and Gonzales\"\", \"\"email\"\": \"\"johnsonashley@exa\",438,None,,,\"[\"\"too\"\", \"\"song\"\", \"\"hand\"\", \"\"customer\"\"]\",,arXiv:2021.73682,,,,,10.4211/HnWV,Nature,2023,Intuitive bi-directional budgetary management\r\n\"Already along example century pressure action. Soldier describe represent resource ground kind.\nArri\",\"[{\"\"name\"\": \"\"Joe Walton\"\", \"\"affiliation\"\": \"\"Anderson PLC\"\", \"\"email\"\": \"\"yvonnebarton@example.org\"\"}, {\"\"name\"\"\",456,None,,,\"[\"\"sell\"\", \"\"eight\"\", \"\"human\"\", \"\"suffer\"\", \"\"toward\"\"]\",,arXiv:2020.99401,,,,,10.9697/Zvpq,Nature,2020,Total tertiary framework\r\nStructure represent agree change almost it. Place travel miss product give every.,\"[{\"\"name\"\": \"\"John Diaz\"\", \"\"affiliation\"\": \"\"Miranda-Tate\"\", \"\"email\"\": \"\"frankmoore@example.net\"\"}, {\"\"name\"\": \"\"\",373,Robertson Group,,,\"[\"\"into\"\", \"\"speech\"\", \"\"than\"\", \"\"process\"\"]\",,arXiv:2023.34425,,,,,10.3176/iAvG,Science,2020,Configurable modular process improvement\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 462
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this YAML data into JSON format:\npaper_id: arXiv:2021.83479\ntitle: Expanded well-modulated protocol\nauthors:\n- name: Rachel Hooper\n affiliation: Johnson, Wright and Cruz\n email: penny02@example.com\n- name: Juan Vargas\n affiliation: Page, Schultz and Howard\n email: richard33@example.net\nabstract: Ask financial cause recognize. Experience attack add its him range. Change\n use why significant her history.\nkeywords:\n- painting\n- have\n- check\npublication:\n venue: Cell\n year: 2020\n doi: 10.7659/Mceh\ncitations: 194\nfunding_source: Carson-Bates\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from YAML 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 \"paper_id\": \"arXiv:2021.83479\",\n \"title\": \"Expanded well-modulated protocol\",\n \"authors\": [\n {\n \"name\": \"Rachel Hooper\",\n \"affiliation\": \"Johnson, Wright and Cruz\",\n \"email\": \"penny02@example.com\"\n },\n {\n \"name\": \"Juan Vargas\",\n \"affiliation\": \"Page, Schultz and Howard\",\n \"email\": \"richard33@example.net\"\n }\n ],\n \"abstract\": \"Ask financial cause recognize. Experience attack add its him range. Change use why significant her history.\",\n \"keywords\": [\n \"painting\",\n \"have\",\n \"check\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2020,\n \"doi\": \"10.7659/Mceh\"\n },\n \"citations\": 194,\n \"funding_source\": \"Carson-Bates\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 252
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics 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<sales_analytics>\n<period>November 2021</period>\n<total_revenue>6206642</total_revenue>\n<units_sold>98463</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>4099651</revenue>\n<growth>36.93</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>4453545</revenue>\n<growth>12.49</growth>\n</channels>\n<top_products>\n<sku>SKU-5933</sku>\n<sales>493873</sales>\n</top_products>\n<top_products>\n<sku>SKU-7813</sku>\n<sales>496083</sales>\n</top_products>\n<top_products>\n<sku>SKU-8482</sku>\n<sales>255782</sales>\n</top_products>\n</sales_analytics>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 223
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\nsignificant,EXP-459167,,,,,Effect of citizen on strong\r\nsignificant,EXP-890471,cohort,262,161,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 42.42, \"\"endpoint\"\": 90.31, \"\"p_value\"\": 0.257}, {\"\"metric\"\": \"\"safety\"\", \",Effect of month on general\r\nsignificant,EXP-932264,observational,302,502,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 87.71, \"\"endpoint\"\": 94.1, \"\"p_value\"\": 0.1199}, {\"\"metric\"\": \"\"efficac\",Effect of personal on pass\r\nsignificant,EXP-496638,cohort,110,483,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 11.71, \"\"endpoint\"\": 28.33, \"\"p_value\"\": 0.1478}, {\"\"metric\"\": \"\"safety\",Effect of everybody on lot\r\nnon-significant,EXP-476589,cohort,36,129,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 82.16, \"\"endpoint\"\": 72.66, \"\"p_value\"\": 0.1811}, {\"\"metric\"\": \"\"safety\",Effect of election on above\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 305
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate clinical note data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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:\nnote_id = \"CN-7319440\"\nencounter_date = \"2026-01-02\"\nchief_complaint = \"headache\"\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"I20\"\n\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"I97\"\n\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"K28\"\n\n[patient]\nmrn = \"MRN-220534\"\nage = 24\ngender = \"M\"\n\n[vitals]\nbp = \"94/79\"\nhr = 69\ntemp_f = 100.9\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 157
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>July 2024</period>\n<total_revenue>3830731</total_revenue>\n<units_sold>4114</units_sold>\n<channels>\n<name>retail</name>\n<revenue>3962653</revenue>\n<growth>41.57</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>752149</revenue>\n<growth>37.04</growth>\n</channels>\n<top_products>\n<sku>SKU-3410</sku>\n<sales>244103</sales>\n</top_products>\n<top_products>\n<sku>SKU-3961</sku>\n<sales>282902</sales>\n</top_products>\n<top_products>\n<sku>SKU-2630</sku>\n<sales>263402</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML 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:\nperiod: July 2024\ntotal_revenue: 3830731\nunits_sold: 4114\nchannels:\n- name: retail\n revenue: 3962653\n growth: 41.57\n- name: wholesale\n revenue: 752149\n growth: 37.04\ntop_products:\n- sku: SKU-3410\n sales: 244103\n- sku: SKU-3961\n sales: 282902\n- sku: SKU-2630\n sales: 263402\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 149
} |
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ncustomer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id\r\nbffcc9bf-c7ad-482d-a457-f67eac39f00a,\"[{\"\"sku\"\": \"\"SKU-87844\"\", \"\"qty\"\": 3, \"\"price\"\": 436.0}, {\"\"sku\"\": \"\"SKU-90224\"\", \"\"qty\"\": 1, \"\"price\"\": 473.23}, {\"\"\",paypal,714.81,120.56,2026-01-07T01:26:14.110632,651.41,TXN-41173343\r\n4ba2d518-d840-4433-ab6f-e5d832ed144c,\"[{\"\"sku\"\": \"\"SKU-61263\"\", \"\"qty\"\": 3, \"\"price\"\": 363.08}, {\"\"sku\"\": \"\"SKU-30806\"\", \"\"qty\"\": 3, \"\"price\"\": 492.39}]\",paypal,1617.64,114.81,2026-01-07T01:26:14.115221,773.58,TXN-34216118\r\n4f73cd61-d0c2-4afc-90a0-4bca0a66d098,\"[{\"\"sku\"\": \"\"SKU-48179\"\", \"\"qty\"\": 2, \"\"price\"\": 80.6}]\",paypal,480.08,141.55,2026-01-07T01:26:14.115310,1301.77,TXN-57245049\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 249
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output sales analytics as JSON."
},
{
"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\": \"August 2021\",\n \"total_revenue\": 4981015,\n \"units_sold\": 45256,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 1659163,\n \"growth\": 5.12\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 436629,\n \"growth\": 13.81\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-2878\",\n \"sales\": 229782\n },\n {\n \"sku\": \"SKU-4457\",\n \"sales\": 274374\n },\n {\n \"sku\": \"SKU-6209\",\n \"sales\": 311056\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
} |
[
{
"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 \"txn_id\": \"TXN-86465796\",\n \"customer_id\": \"8f239cfc-bdbc-4a82-9121-b588096e290b\",\n \"timestamp\": \"2026-01-07T01:26:12.345353\",\n \"items\": [\n {\n \"sku\": \"SKU-78354\",\n \"qty\": 1,\n \"price\": 289.73\n },\n {\n \"sku\": \"SKU-13609\",\n \"qty\": 1,\n \"price\": 322.15\n },\n {\n \"sku\": \"SKU-34282\",\n \"qty\": 5,\n \"price\": 483.05\n }\n ],\n \"subtotal\": 706.99,\n \"tax\": 109.65,\n \"total\": 529.31,\n \"payment_method\": \"apple_pay\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record 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<transaction_record>\n<txn_id>TXN-86465796</txn_id>\n<customer_id>8f239cfc-bdbc-4a82-9121-b588096e290b</customer_id>\n<timestamp>2026-01-07T01:26:12.345353</timestamp>\n<items>\n<sku>SKU-78354</sku>\n<qty>1</qty>\n<price>289.73</price>\n</items>\n<items>\n<sku>SKU-13609</sku>\n<qty>1</qty>\n<price>322.15</price>\n</items>\n<items>\n<sku>SKU-34282</sku>\n<qty>5</qty>\n<price>483.05</price>\n</items>\n<subtotal>706.99</subtotal>\n<tax>109.65</tax>\n<total>529.31</total>\n<payment_method>apple_pay</payment_method>\n</transaction_record>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 218
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/part_get_parameters,paths_/part_get_responses_200_description,paths_/part_get_responses_400_description,paths_/part_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Re-contextualized motivating extranet API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Expect be live house.,,,,\r\nTwo well indicate under. Ability before science million report.,\"[{\"\"name\"\": \"\"James Nelson\"\", \"\"affiliation\"\": \"\"Mendoza-Black\"\", \"\"email\"\": \"\"qrowe@example.com\"\"}, {\"\"name\"\": \"\"J\",289,None,,,\"[\"\"green\"\", \"\"certain\"\", \"\"station\"\", \"\"agree\"\", \"\"network\"\"]\",,arXiv:2021.59218,,,,,10.3952/rslp,Science,2022,Robust bifurcated Graphical User Interface\r\n\"Result table Mr only school state impact.\nWind forward art claim air former little. Son full gas.\",\"[{\"\"name\"\": \"\"Charles Weeks\"\", \"\"affiliation\"\": \"\"Warren-Phillips\"\", \"\"email\"\": \"\"uschaefer@example.net\"\"}, {\"\"na\",140,None,,,\"[\"\"eat\"\", \"\"turn\"\", \"\"nothing\"\", \"\"job\"\"]\",,arXiv:2021.92505,,,,,10.2780/eGhQ,Cell,2022,Managed well-modulated budgetary management\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 384
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate api specification data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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 \"info\": {\n \"title\": \"Persevering explicit access API\",\n \"version\": \"1.0.0\"\n },\n \"openapi\": \"3.0.0\",\n \"paths\": {\n \"/seek\": {\n \"get\": {\n \"summary\": \"Part fill speech.\",\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}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 268
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n,chest pain,2026-01-05,CN-9050287,,,,163/70,116,98.5\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J74\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J20\"\"}, {\"\"problem\"\": \"\"\",fever,2026-01-03,CN-7100334,63,F,MRN-871288,157/73,66,98.1\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I30\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K37\"\"}]\",headache,2026-01-01,CN-6107262,52,F,MRN-618009,128/101,89,102.9\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K29\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J52\"\"}, {\"\"problem\"\": \"\"\",fever,2026-01-06,CN-8266502,77,F,MRN-463655,117/71,106,100.2\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 256
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate product listing data in JSON format."
},
{
"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-602506\",\n \"name\": \"Diverse 5thgeneration monitoring\",\n \"category\": \"electronics\",\n \"price\": 469.91,\n \"currency\": \"USD\",\n \"stock\": 372,\n \"is_available\": true,\n \"rating\": 3.7,\n \"reviews\": 813,\n \"specs\": {\n \"weight_kg\": 26.31,\n \"dimensions\": \"49x82x12cm\"\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 151
} |
[
{
"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: 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 \"note_id\": \"CN-1302322\",\n \"patient\": {\n \"mrn\": \"MRN-805550\",\n \"age\": 78,\n \"gender\": \"M\"\n },\n \"encounter_date\": \"2026-01-06\",\n \"chief_complaint\": \"chest pain\",\n \"vitals\": {\n \"bp\": \"163/88\",\n \"hr\": 113,\n \"temp_f\": 97.8\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"K43\"\n },\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J96\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output product listing as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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 \"product_id\": \"PROD-488153\",\n \"name\": \"Reactive dynamic adapter\",\n \"category\": \"books\",\n \"price\": 843.52,\n \"currency\": \"USD\",\n \"stock\": 615,\n \"is_available\": true,\n \"rating\": 1.77,\n \"reviews\": 503,\n \"specs\": {\n \"weight_kg\": 17.5,\n \"dimensions\": \"49x57x63cm\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 148
} |
[
{
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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 \"course_id\": \"CRS-5591\",\n \"code\": \"WID449\",\n \"title\": \"Proactive solution-oriented secured line 101\",\n \"instructor\": \"Gabriella Scott DDS\",\n \"credits\": 3,\n \"term\": \"Fall 2020\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"final\"\n },\n {\n \"week\": 2,\n \"topic\": \"character\"\n },\n {\n \"week\": 3,\n \"topic\": \"treatment\"\n },\n {\n \"week\": 4,\n \"topic\": \"serious\"\n },\n {\n \"week\": 5,\n \"topic\": \"store\"\n },\n {\n \"week\": 6,\n \"topic\": \"according\"\n },\n {\n \"week\": 7,\n \"topic\": \"deep\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 244
} |
[
{
"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 JSON to YAML:\n{\n \"note_id\": \"CN-9635412\",\n \"patient\": {\n \"mrn\": \"MRN-739596\",\n \"age\": 36,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-01\",\n \"chief_complaint\": \"chest pain\",\n \"vitals\": {\n \"bp\": \"180/102\",\n \"hr\": 103,\n \"temp_f\": 99.3\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"K43\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J43\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"K99\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note 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:\nnote_id: CN-9635412\npatient:\n mrn: MRN-739596\n age: 36\n gender: F\nencounter_date: '2026-01-01'\nchief_complaint: chest pain\nvitals:\n bp: 180/102\n hr: 103\n temp_f: 99.3\nassessment:\n- problem: diabetes\n icd10: K43\n- problem: hypertension\n icd10: J43\n- problem: hypertension\n icd10: K99\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 151
} |
[
{
"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 \"error_id\": \"14ae8ed3-6b55-40da-8ce1-0df499a5acbd\",\n \"timestamp\": \"2026-01-07T01:26:12.379465\",\n \"level\": \"CRITICAL\",\n \"service\": \"niceService\",\n \"message\": \"Right at clear respond.\",\n \"stack_trace\": [\n \"at between.py:225\",\n \"at lose.py:411\",\n \"at direction.py:43\",\n \"at administration.py:283\"\n ],\n \"context\": {\n \"user_id\": \"d688d508-33f3-4d4c-9bea-5907cdf56165\",\n \"request_id\": \"7a356b03-06c2-4f7a-942e-f59608baa9dd\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log 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<error_log>\n<error_id>14ae8ed3-6b55-40da-8ce1-0df499a5acbd</error_id>\n<timestamp>2026-01-07T01:26:12.379465</timestamp>\n<level>CRITICAL</level>\n<service>niceService</service>\n<message>Right at clear respond.</message>\n<stack_trace>at between.py:225</stack_trace>\n<stack_trace>at lose.py:411</stack_trace>\n<stack_trace>at direction.py:43</stack_trace>\n<stack_trace>at administration.py:283</stack_trace>\n<context>\n<user_id>d688d508-33f3-4d4c-9bea-5907cdf56165</user_id>\n<request_id>7a356b03-06c2-4f7a-942e-f59608baa9dd</request_id>\n</context>\n</error_log>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 225
} |
[
{
"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 JSON to YAML:\n{\n \"company\": \"Kaiser-Andrews\",\n \"ticker\": \"WULG\",\n \"quarter\": \"Q4 2022\",\n \"revenue\": 97370821,\n \"expenses\": 78723404,\n \"net_income\": 9585923,\n \"eps\": 9.85,\n \"metrics\": {\n \"profit_margin\": 23.02,\n \"roe\": 16.56\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from JSON 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:\ncompany: Kaiser-Andrews\nticker: WULG\nquarter: Q4 2022\nrevenue: 97370821\nexpenses: 78723404\nnet_income: 9585923\neps: 9.85\nmetrics:\n profit_margin: 23.02\n roe: 16.56\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 121
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Secured zero-defect leverage API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</only>\n<get>\n<summary>Probably begin everybody.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//only>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 195
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output course syllabus as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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:\ncourse_id: CRS-9301\ncode: PHF438\ntitle: Proactive asynchronous moderator 101\ninstructor: Karen Meadows\ncredits: 4\nterm: Spring 2023\nschedule:\n- week: 1\n topic: eight\n- week: 2\n topic: above\n- week: 3\n topic: run\n- week: 4\n topic: continue\n- week: 5\n topic: now\n- week: 6\n topic: travel\n- week: 7\n topic: religious\n- week: 8\n topic: 'yes'\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 177
} |
[
{
"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 YAML to JSON:\nprescriber: Tiffany Sanchez\ndate: '2026-01-01'\nrx_id: RX-4079006\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from YAML 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 \"prescriber\": \"Tiffany Sanchez\",\n \"date\": \"2026-01-01\",\n \"rx_id\": \"RX-4079006\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 101
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K16\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J24\"\"}, {\"\"problem\"\": \"\"\",headache,2026-01-06,CN-9833890,43,F,MRN-321038,156/88,75,101.8\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K67\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K96\"\"}, {\"\"problem\",chest pain,2026-01-06,CN-2175601,48,M,MRN-946814,114/93,75,102.9\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K29\"\"}]\",chest pain,2026-01-03,CN-9051107,24,M,MRN-130502,164/107,75,100.0\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K40\"\"}]\",headache,2026-01-05,CN-7691091,62,F,MRN-653197,178/86,63,98.3\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J47\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I67\"\"}, {\"\"problem\",fever,2026-01-02,CN-2405188,23,F,MRN-461237,165/104,84,101.6\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 307
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<assessment_id>ASMT-324605</assessment_id>\n<student_id>STU-156768</student_id>\n<course_id>CRS-7632</course_id>\n<type>assignment</type>\n<date>2026-01-04</date>\n<scores>\n<question>1</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>86</total_score>\n<percentage>70.59</percentage>\n<grade>B</grade>\n</student_assessment>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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:\nassessment_id: ASMT-324605\nstudent_id: STU-156768\ncourse_id: CRS-7632\ntype: assignment\ndate: '2026-01-04'\nscores:\n- question: 1\n points_earned: 9\n points_possible: 10\n- question: 2\n points_earned: 4\n points_possible: 10\n- question: 3\n points_earned: 2\n points_possible: 10\n- question: 4\n points_earned: 4\n points_possible: 10\n- question: 5\n points_earned: 9\n points_possible: 10\n- question: 6\n points_earned: 3\n points_possible: 10\n- question: 7\n points_earned: 5\n points_possible: 10\n- question: 8\n points_earned: 0\n points_possible: 10\n- question: 9\n points_earned: 6\n points_possible: 10\n- question: 10\n points_earned: 10\n points_possible: 10\n- question: 11\n points_earned: 5\n points_possible: 10\ntotal_score: 86\npercentage: 70.59\ngrade: B\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 271
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output transaction record as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ncustomer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id\r\n56902016-58a3-4ec6-9297-89a851347de3,\"[{\"\"sku\"\": \"\"SKU-99170\"\", \"\"qty\"\": 4, \"\"price\"\": 298.54}, {\"\"sku\"\": \"\"SKU-20363\"\", \"\"qty\"\": 4, \"\"price\"\": 23.88}]\",credit_card,1309.44,144.52,2026-01-07T01:26:14.916908,1761.43,TXN-50723551\r\nb3629e43-4e9c-42b6-a6ec-9a87338984b4,\"[{\"\"sku\"\": \"\"SKU-57366\"\", \"\"qty\"\": 2, \"\"price\"\": 53.84}]\",paypal,382.5,13.18,2026-01-07T01:26:14.918005,445.78,TXN-16191083\r\n5e74e6fb-d478-4649-b80e-fd0f6ebb647f,\"[{\"\"sku\"\": \"\"SKU-89853\"\", \"\"qty\"\": 4, \"\"price\"\": 470.3}, {\"\"sku\"\": \"\"SKU-41708\"\", \"\"qty\"\": 4, \"\"price\"\": 154.98}, {\"\"\",credit_card,1137.44,138.1,2026-01-07T01:26:14.918061,1658.41,TXN-25281974\r\n3b9dc721-2c31-4606-8a77-8fdcbe7a2cfa,\"[{\"\"sku\"\": \"\"SKU-30235\"\", \"\"qty\"\": 5, \"\"price\"\": 350.95}, {\"\"sku\"\": \"\"SKU-51726\"\", \"\"qty\"\": 5, \"\"price\"\": 319.01}, {\",credit_card,825.97,70.93,2026-01-07T01:26:14.918108,1362.06,TXN-58264601\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 309
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate transaction record data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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<transaction_record>\n<txn_id>TXN-46065837</txn_id>\n<customer_id>dcc085d4-ca03-463a-a9b5-157b38cd0e07</customer_id>\n<timestamp>2026-01-07T01:26:12.612650</timestamp>\n<items>\n<sku>SKU-85146</sku>\n<qty>2</qty>\n<price>497.36</price>\n</items>\n<items>\n<sku>SKU-77940</sku>\n<qty>1</qty>\n<price>153.37</price>\n</items>\n<items>\n<sku>SKU-99115</sku>\n<qty>5</qty>\n<price>476.22</price>\n</items>\n<items>\n<sku>SKU-69141</sku>\n<qty>3</qty>\n<price>169.13</price>\n</items>\n<subtotal>1921.97</subtotal>\n<tax>84.11</tax>\n<total>783.92</total>\n<payment_method>paypal</payment_method>\n</transaction_record>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 234
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate course syllabus data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nTPD420,CRS-9108,3,40,30,30,Eddie Baker,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"allow\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"note\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"find\"\"}, {\"\"week\"\":\",Fall 2024,Polarized content-based middleware 101\r\nLJW233,CRS-7590,3,40,30,30,Margaret Crawford,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"care\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"one\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"condition\"\"}, {\"\"wee\",Spring 2023,Right-sized fault-tolerant website 101\r\nREH205,CRS-2775,3,40,30,30,Daniel Jensen,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"site\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"at\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"total\"\"}, {\"\"week\"\": 4\",Fall 2023,Reduced foreground capacity 101\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 262
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate course syllabus data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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 \"course_id\": \"CRS-7399\",\n \"code\": \"VAQ490\",\n \"title\": \"Ameliorated explicit migration 101\",\n \"instructor\": \"Tammy Griffith\",\n \"credits\": 4,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"media\"\n },\n {\n \"week\": 2,\n \"topic\": \"chair\"\n },\n {\n \"week\": 3,\n \"topic\": \"perhaps\"\n },\n {\n \"week\": 4,\n \"topic\": \"concern\"\n },\n {\n \"week\": 5,\n \"topic\": \"focus\"\n },\n {\n \"week\": 6,\n \"topic\": \"will\"\n },\n {\n \"week\": 7,\n \"topic\": \"order\"\n },\n {\n \"week\": 8,\n \"topic\": \"several\"\n },\n {\n \"week\": 9,\n \"topic\": \"military\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 265
} |
[
{
"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: b7c34b47-4e4a-4c41-888f-ff64a1b8d06d\ntimestamp: '2026-01-07T01:26:14.918711'\nlevel: WARNING\nservice: discussService\nmessage: Hot outside inside consumer test.\nstack_trace:\n- at game.py:441\n- at activity.py:14\n- at administration.py:426\n- at modern.py:89\ncontext:\n user_id: e8605dad-78b4-4d4e-8061-41a780440a5f\n request_id: 77c8a2c4-4277-4222-81f1-817bd0da301c\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 169
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course_id>CRS-5796</course_id>\n<code>BSI420</code>\n<title>Expanded needs-based hub 101</title>\n<instructor>Sarah Collins</instructor>\n<credits>3</credits>\n<term>Fall 2022</term>\n<schedule>\n<week>1</week>\n<topic>number</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>single</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>personal</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>our</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>consumer</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>trouble</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>tree</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>firm</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>range</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>over</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus 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:\ncourse_id: CRS-5796\ncode: BSI420\ntitle: Expanded needs-based hub 101\ninstructor: Sarah Collins\ncredits: 3\nterm: Fall 2022\nschedule:\n- week: 1\n topic: number\n- week: 2\n topic: single\n- week: 3\n topic: personal\n- week: 4\n topic: our\n- week: 5\n topic: consumer\n- week: 6\n topic: trouble\n- week: 7\n topic: tree\n- week: 8\n topic: firm\n- week: 9\n topic: range\n- week: 10\n topic: over\n- week: 11\n topic: want\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 194
} |
[
{
"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 \"course_id\": \"CRS-9108\",\n \"code\": \"TPD420\",\n \"title\": \"Polarized content-based middleware 101\",\n \"instructor\": \"Eddie Baker\",\n \"credits\": 3,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"allow\"\n },\n {\n \"week\": 2,\n \"topic\": \"note\"\n },\n {\n \"week\": 3,\n \"topic\": \"find\"\n },\n {\n \"week\": 4,\n \"topic\": \"main\"\n },\n {\n \"week\": 5,\n \"topic\": \"Mrs\"\n },\n {\n \"week\": 6,\n \"topic\": \"give\"\n },\n {\n \"week\": 7,\n \"topic\": \"sense\"\n },\n {\n \"week\": 8,\n \"topic\": \"community\"\n },\n {\n \"week\": 9,\n \"topic\": \"these\"\n },\n {\n \"week\": 10,\n \"topic\": \"possible\"\n },\n {\n \"week\": 11,\n \"topic\": \"soldier\"\n }\n ],\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 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-9108\ncode: TPD420\ntitle: Polarized content-based middleware 101\ninstructor: Eddie Baker\ncredits: 3\nterm: Fall 2024\nschedule:\n- week: 1\n topic: allow\n- week: 2\n topic: note\n- week: 3\n topic: find\n- week: 4\n topic: main\n- week: 5\n topic: Mrs\n- week: 6\n topic: give\n- week: 7\n topic: sense\n- week: 8\n topic: community\n- week: 9\n topic: these\n- week: 10\n topic: possible\n- week: 11\n topic: soldier\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 196
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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 \"assessment_id\": \"ASMT-481147\",\n \"student_id\": \"STU-291176\",\n \"course_id\": \"CRS-7846\",\n \"type\": \"exam\",\n \"date\": \"2026-01-03\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 10,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 91,\n \"percentage\": 55.23,\n \"grade\": \"C\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 353
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output financial report as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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:\nnet_income: 1392290\nticker: NEEN\nquarter: Q2 2023\nexpenses: 22857500\nrevenue: 21273983\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 101
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate sales analytics data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics 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<sales_analytics>\n<period>January 2022</period>\n<total_revenue>5531867</total_revenue>\n<units_sold>51554</units_sold>\n<channels>\n<name>online</name>\n<revenue>2281841</revenue>\n<growth>12.7</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>1714859</revenue>\n<growth>33.17</growth>\n</channels>\n<top_products>\n<sku>SKU-2323</sku>\n<sales>285676</sales>\n</top_products>\n<top_products>\n<sku>SKU-2670</sku>\n<sales>378071</sales>\n</top_products>\n<top_products>\n<sku>SKU-6091</sku>\n<sales>425037</sales>\n</top_products>\n</sales_analytics>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 222
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate error log data in JSON format."
},
{
"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\": \"7fb310a3-c37c-4709-86ce-e1b5db3f92d9\",\n \"timestamp\": \"2026-01-07T01:26:14.428646\",\n \"level\": \"CRITICAL\",\n \"service\": \"mouthService\",\n \"message\": \"Why do feeling mouth bad.\",\n \"stack_trace\": [\n \"at home.py:277\",\n \"at travel.py:169\"\n ],\n \"context\": {\n \"user_id\": \"f4ae6ac7-8454-4688-900a-4755a2618c97\",\n \"request_id\": \"d209edd5-fa8e-4cee-a09e-a65f81e6a700\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 175
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate experiment result data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\nnon-significant,EXP-949926,observational,190,113,,Effect of mean on gun\r\nsignificant,EXP-501187,RCT,299,800,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 96.65, \"\"endpoint\"\": 44.16, \"\"p_value\"\": 0.4231}, {\"\"metric\"\": \"\"safety\"\",\",Effect of audience on sit\r\nnon-significant,EXP-718111,RCT,306,146,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 31.23, \"\"endpoint\"\": 75.55, \"\"p_value\"\": 0.4638}, {\"\"metric\"\": \"\"safety\",Effect of sea on learn\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 213
} |
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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<news_article>\n<article_id>ART-5303643</article_id>\n<headline>Cloned discrete secured line</headline>\n<author>Mathew Nelson</author>\n<published>2026-01-04T09:57:36.673621</published>\n<section>Tech</section>\n<content>Himself difference kid your and. Mission memory ten argue by note happy. Country tax impact wonder listen.\nKeep big lot hit. Nation figure tend yard wonder home. Some list compare remember scene.\nOld specific until house not ahead. Case pass exist condition. Administration stay save owner.</content>\n<tags>election</tags>\n<tags>might</tags>\n<tags>idea</tags>\n<tags>debate</tags>\n<tags>city</tags>\n<views>22731</views>\n<shares>1661</shares>\n</news_article>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 254
} |
[
{
"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 CSV to JSON:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-2017273,Craig Chen,,,,,,\"[\"\"away\"\", \"\"adult\"\", \"\"happen\"\", \"\"adult\"\"]\",59537\r\nART-2454776,Cynthia Figueroa,\"Always get determine our person.\nNever man land choose employee.\nKid room because candidate others f\",Multi-lateral 4thgeneration solution,2026-01-06T13:49:13.866939,Tech,1365,\"[\"\"every\"\", \"\"memory\"\", \"\"station\"\", \"\"soon\"\", \"\"light\"\"]\",74794\r\nART-6698856,Kimberly Ryan,Concern serious situation color. Build leader rest alone fear moment yourself. Wrong show task altho,Assimilated heuristic strategy,2026-01-04T06:37:57.076882,Politics,4125,\"[\"\"government\"\", \"\"life\"\", \"\"carry\"\"]\",3167\r\nART-9215581,Alex Adkins,\"Design all street finally environment moment recognize. Defense prepare field sport central.\nMoment \",Managed responsive help-desk,2026-01-05T22:52:42.100863,Politics,2666,\"[\"\"idea\"\", \"\"feel\"\", \"\"north\"\", \"\"eight\"\"]\",36328\r\nART-9821549,Jonathan Blankenship,\"Phone old must none simple each. Question cup represent. Travel building dark improve throughout.\nSo\",Sharable stable artificial intelligence,2026-01-01T02:39:43.132531,Politics,1483,\"[\"\"traditional\"\", \"\"program\"\", \"\"laugh\"\", \"\"manage\"\"]\",33145\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from CSV 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 \"views\": 59537,\n \"article_id\": \"ART-2017273\",\n \"tags\": [\n \"away\",\n \"adult\",\n \"happen\",\n \"adult\"\n ],\n \"author\": \"Craig Chen\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 115
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate error log data in TOML format."
},
{
"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 = \"fa94040b-9882-4000-8e09-a7e4dff1626b\"\ntimestamp = \"2026-01-07T01:26:12.350355\"\nlevel = \"CRITICAL\"\nservice = \"defenseService\"\nmessage = \"Speak community factor agency plant would business difficult.\"\nstack_trace = [ \"at city.py:448\", \"at final.py:495\", \"at go.py:294\", \"at pull.py:288\",]\n\n[context]\nuser_id = \"e4012d07-bfd2-4476-9588-083fd5101bd4\"\nrequest_id = \"fc835e46-ae3b-4064-af44-5b40a2727b3e\"\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 175
} |
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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 \"company\": \"Craig, Clark and Kent\",\n \"ticker\": \"PIOR\",\n \"quarter\": \"Q2 2024\",\n \"revenue\": 6156154,\n \"expenses\": 34396688,\n \"net_income\": 15229291,\n \"eps\": 5.77,\n \"metrics\": {\n \"profit_margin\": 10.65,\n \"roe\": 13.61\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 137
} |
[
{
"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: 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:\ncourse_id: CRS-6754\ncode: NGM306\ntitle: User-centric bottom-line Local Area Network 101\ninstructor: Shannon Gonzalez\ncredits: 3\nterm: Spring 2020\nschedule:\n- week: 1\n topic: much\n- week: 2\n topic: little\n- week: 3\n topic: station\n- week: 4\n topic: call\n- week: 5\n topic: watch\n- week: 6\n topic: close\n- week: 7\n topic: mention\n- week: 8\n topic: direction\n- week: 9\n topic: study\n- week: 10\n topic: analysis\n- week: 11\n topic: discuss\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 202
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate customer review data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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:\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,\"You woman when. Night collection whole officer along skin.\nExample against need. Likely you good eff\",,2026-01-05,48,,,,PROD-463913,4,REV-8045456,,,,,Per responsibility past green trip.,ba642a1e-c9a9-4bbb-9297-90eddc75d10f,True\r\nbooks,,USD,,,True,Function-based solution-oriented policy,189.22,PROD-668912,1.0,,924,97x66x11cm,32.55,167,,,\r\nelectronics,,USD,,,True,Assimilated exuding structure,582.63,PROD-725737,3.31,,659,100x49x79cm,13.16,264,,,\r\nbooks,,USD,,,True,Distributed analyzing approach,417.85,PROD-543089,4.18,,156,84x28x42cm,48.27,423,,,\r\nclothing,,USD,,,True,Expanded stable customer loyalty,852.29,PROD-253638,2.53,,933,88x13x76cm,19.64,683,,,\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 287
} |
[
{
"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>d70fbe2a-d8f3-4de3-b2fc-9d88b4848f07</error_id>\n<timestamp>2026-01-07T01:26:11.601023</timestamp>\n<level>ERROR</level>\n<service>trainingService</service>\n<message>Policy myself generation deal training.</message>\n<stack_trace>at would.py:424</stack_trace>\n<stack_trace>at bill.py:423</stack_trace>\n<stack_trace>at address.py:201</stack_trace>\n<stack_trace>at where.py:106</stack_trace>\n<context>\n<user_id>f63438a7-9c62-4606-a470-11f5586d45be</user_id>\n<request_id>da97ea84-2ecf-4247-a224-b1f181cc3986</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\": \"d70fbe2a-d8f3-4de3-b2fc-9d88b4848f07\",\n \"timestamp\": \"2026-01-07T01:26:11.601023\",\n \"level\": \"ERROR\",\n \"service\": \"trainingService\",\n \"message\": \"Policy myself generation deal training.\",\n \"stack_trace\": [\n \"at would.py:424\",\n \"at bill.py:423\",\n \"at address.py:201\",\n \"at where.py:106\"\n ],\n \"context\": {\n \"user_id\": \"f63438a7-9c62-4606-a470-11f5586d45be\",\n \"request_id\": \"da97ea84-2ecf-4247-a224-b1f181cc3986\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 192
} |
[
{
"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<experiment_result>\n<experiment_id>EXP-977504</experiment_id>\n<title>Effect of strong on relationship</title>\n<methodology>\n<design>cohort</design>\n<sample_size>875</sample_size>\n<duration_days>181</duration_days>\n</methodology>\n<results>\n<metric>efficacy</metric>\n<baseline>55.49</baseline>\n<endpoint>52.36</endpoint>\n<p_value>0.0911</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>52.32</baseline>\n<endpoint>84.09</endpoint>\n<p_value>0.0602</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>46.27</baseline>\n<endpoint>10.72</endpoint>\n<p_value>0.2329</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: 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 \"experiment_id\": \"EXP-977504\",\n \"title\": \"Effect of strong on relationship\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 875,\n \"duration_days\": 181\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 55.49,\n \"endpoint\": 52.36,\n \"p_value\": 0.0911\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 52.32,\n \"endpoint\": 84.09,\n \"p_value\": 0.0602\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 46.27,\n \"endpoint\": 10.72,\n \"p_value\": 0.2329\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 224
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output course syllabus as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nFIN264,CRS-3498,,,,,,,Spring 2021,\r\nEEX489,CRS-5967,4,40,30,30,Tracy Schroeder,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"boy\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"maintain\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"act\"\"}, {\"\"week\"\"\",Spring 2024,Total radical hub 101\r\nZAS202,CRS-3653,4,40,30,30,Traci Ford,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"we\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"grow\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"world\"\"}, {\"\"week\"\": 4\",Spring 2022,Intuitive attitude-oriented functionalities 101\r\nZBS270,CRS-3463,3,40,30,30,Wendy Stafford,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"property\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"star\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"institution\"\"}\",Fall 2022,Future-proofed intangible Graphic Interface 101\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 274
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn_id>TXN-63103340</txn_id>\n<customer_id>dcc4c9a4-da2c-4d2f-a3fa-df68956ce256</customer_id>\n<timestamp>2026-01-07T01:26:10.781600</timestamp>\n<payment_method>apple_pay</payment_method>\n<items>\n<sku>SKU-96277</sku>\n<qty>1</qty>\n<price>321.56</price>\n</items>\n<items>\n<sku>SKU-42742</sku>\n<qty>3</qty>\n<price>191.74</price>\n</items>\n<items>\n<sku>SKU-55194</sku>\n<qty>4</qty>\n<price>118.72</price>\n</items>\n<items>\n<sku>SKU-97759</sku>\n<qty>4</qty>\n<price>166.31</price>\n</items>\n</transaction_record>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record from XML to 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. Transform values to match the target format specifications.\n\nOutput:\ntxn_id: TXN-63103340\ncustomer_id: dcc4c9a4-da2c-4d2f-a3fa-df68956ce256\ntimestamp: '2026-01-07T01:26:10.781600'\npayment_method: apple_pay\nitems:\n- sku: SKU-96277\n qty: 1\n price: 321.56\n- sku: SKU-42742\n qty: 3\n price: 191.74\n- sku: SKU-55194\n qty: 4\n price: 118.72\n- sku: SKU-97759\n qty: 4\n price: 166.31\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 159
} |
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-1000724,Brandon Kaiser,\"Order doctor person official. Seek make eight like plan. Off table stop friend.\nHospital owner mean \",Profound background open architecture,2026-01-03T02:42:32.546717,Politics,2461,\"[\"\"natural\"\", \"\"present\"\", \"\"subject\"\"]\",23859\r\nART-9187319,Jeffrey Gould,\"Value affect bag space. Good body someone eat most challenge ask.\nArt growth matter mean manage fina\",Synergistic holistic benchmark,2026-01-02T19:57:33.500646,Politics,3041,\"[\"\"leave\"\", \"\"if\"\", \"\"already\"\", \"\"mean\"\", \"\"along\"\"]\",34313\r\nART-3508411,Andrew Shields,\"Kind animal our choice. Office budget care event through nothing career.\nChance president the west. \",Cloned bandwidth-monitored Graphical User Interface,2026-01-05T22:59:44.280908,Tech,2306,\"[\"\"large\"\", \"\"about\"\", \"\"ask\"\"]\",75324\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 290
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output prescription as TOML."
},
{
"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-6847501\"\npatient_mrn = \"MRN-637576\"\nprescriber = \"Victor Boyd\"\ndate = \"2026-01-06\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"20mg\"\nfrequency = \"TID\"\nquantity = 30\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"20mg\"\nfrequency = \"daily\"\nquantity = 90\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"5mg\"\nfrequency = \"TID\"\nquantity = 30\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 161
} |
[
{
"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 JSON to YAML:\n{\n \"post_id\": \"POST-45290210\",\n \"platform\": \"instagram\",\n \"user_id\": \"bbb035d4-0f61-413b-897c-cd72fa595a38\",\n \"username\": \"monicabaker\",\n \"content\": \"Administration any add. Tough pick turn may church worry.\\nLeft federal know risk bank. Degree out provide relate west writer age.\",\n \"timestamp\": \"2026-01-07T01:26:14.663547\",\n \"hashtags\": [\n \"#of\",\n \"#turn\",\n \"#present\"\n ],\n \"engagement\": {\n \"likes\": 8210,\n \"shares\": 180,\n \"comments\": 67\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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:\npost_id: POST-45290210\nplatform: instagram\nuser_id: bbb035d4-0f61-413b-897c-cd72fa595a38\nusername: monicabaker\ncontent: 'Administration any add. Tough pick turn may church worry.\n\n Left federal know risk bank. Degree out provide relate west writer age.'\ntimestamp: '2026-01-07T01:26:14.663547'\nhashtags:\n- '#of'\n- '#turn'\n- '#present'\nengagement:\n likes: 8210\n shares: 180\n comments: 67\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 177
} |
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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:\ncitations: 25\nkeywords:\n- determine\n- hope\n- purpose\n- want\n- expert\ntitle: Face-to-face radical projection\npaper_id: arXiv:2024.39920\nfunding_source: null\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 117
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate product listing data in CSV format."
},
{
"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,Phased real-time system engine,748.72,PROD-442175,4.21,544,32x58x41cm,42.73,660\r\nbooks,USD,True,De-engineered 24hour encryption,262.98,PROD-776771,2.64,729,31x74x59cm,42.08,679\r\nelectronics,USD,True,Universal 4thgeneration flexibility,214.42,PROD-388273,3.49,105,43x56x71cm,37.08,278\r\nclothing,USD,True,Compatible 24/7 task-force,694.75,PROD-223267,1.84,824,35x46x75cm,36.33,777\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 202
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output experiment result as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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 \"experiment_id\": \"EXP-565695\",\n \"title\": \"Effect of toward on stop\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 107,\n \"duration_days\": 350\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 72.19,\n \"endpoint\": 65.67,\n \"p_value\": 0.4453\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 42.8,\n \"endpoint\": 19.76,\n \"p_value\": 0.4179\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 32.32,\n \"endpoint\": 41.26,\n \"p_value\": 0.0031\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 220
} |
[
{
"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<title>Us guess foreign amount experience modern sister w</title>\n<date>2026-01-01</date>\n<rating>4</rating>\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\": \"Us guess foreign amount experience modern sister w\",\n \"date\": \"2026-01-01\",\n \"rating\": 4\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 106
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output news article as YAML."
},
{
"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-4984184\nheadline: Face-to-face clear-thinking interface\nauthor: Joshua Dennis\npublished: '2026-01-01T01:03:44.687449'\nsection: Business\ncontent: 'Center state probably. Ever quickly order college respond charge.\n\n Walk particularly anyone effect without. Contain public yard news ahead direction.\n\n Mention phone international report according. Sell garden turn movie old. Buy simple\n necessary early use leg.'\ntags:\n- real\n- system\n- benefit\n- away\n- fight\nviews: 75186\nshares: 4472\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 203
} |
[
{
"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:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\nnon-significant,EXP-927626,observational,55,73,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 27.12, \"\"endpoint\"\": 99.68, \"\"p_value\"\": 0.1097}, {\"\"metric\"\": \"\"efficacy\",Effect of I on station\r\nnon-significant,EXP-616214,observational,147,950,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 31.73, \"\"endpoint\"\": 31.17, \"\"p_value\"\": 0.042}, {\"\"metric\"\": \"\"efficacy\"\"\",Effect of station on seat\r\nsignificant,EXP-693349,RCT,100,351,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 46.45, \"\"endpoint\"\": 38.35, \"\"p_value\"\": 0.1335}, {\"\"metric\"\": \"\"safety\",Effect of serious on for\r\nnon-significant,EXP-246823,observational,272,473,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 14.57, \"\"endpoint\"\": 98.77, \"\"p_value\"\": 0.2034}, {\"\"metric\"\": \"\"safety\",Effect of rich on far\r\nnon-significant,EXP-683096,cohort,181,218,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 41.55, \"\"endpoint\"\": 69.55, \"\"p_value\"\": 0.2904}, {\"\"metric\"\": \"\"safety\",Effect of although on fight\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from CSV 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 \"experiment_id\": \"EXP-927626\",\n \"title\": \"Effect of I on station\",\n \"methodology\": {\n \"design\": \"observational\",\n \"sample_size\": 73,\n \"duration_days\": 55\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 27.12,\n \"endpoint\": 99.68,\n \"p_value\": 0.1097\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 42.57,\n \"endpoint\": 79.28,\n \"p_value\": 0.1217\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 29.93,\n \"endpoint\": 73.02,\n \"p_value\": 0.1364\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 73.56,\n \"endpoint\": 65.43,\n \"p_value\": 0.4249\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 251
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate api specification data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Intuitive fault-tolerant service-desk API\"\nversion = \"1.0.0\"\n\n[paths.\"/behavior\".get]\nsummary = \"Play remain value only head land perform.\"\n[[paths.\"/behavior\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/behavior\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/behavior\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 172
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output api specification as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Business-focused composite flexibility API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</total>\n<get>\n<summary>Building public truth decade.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//total>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 220
} |
[
{
"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: 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:\ncourse_id: CRS-5796\ncode: BSI420\ntitle: Expanded needs-based hub 101\ninstructor: Sarah Collins\ncredits: 3\nterm: Fall 2022\nschedule:\n- week: 1\n topic: number\n- week: 2\n topic: single\n- week: 3\n topic: personal\n- week: 4\n topic: our\n- week: 5\n topic: consumer\n- week: 6\n topic: trouble\n- week: 7\n topic: tree\n- week: 8\n topic: firm\n- week: 9\n topic: range\n- week: 10\n topic: over\n- week: 11\n topic: want\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 193
} |
[
{
"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 JSON to YAML:\n{\n \"assessment_id\": \"ASMT-809817\",\n \"student_id\": \"STU-889156\",\n \"course_id\": \"CRS-6947\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-05\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 13,\n \"points_earned\": 5,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 92,\n \"percentage\": 67.34,\n \"grade\": \"A\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from JSON 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:\nassessment_id: ASMT-809817\nstudent_id: STU-889156\ncourse_id: CRS-6947\ntype: assignment\ndate: '2026-01-05'\nscores:\n- question: 1\n points_earned: 7\n points_possible: 10\n- question: 2\n points_earned: 9\n points_possible: 10\n- question: 3\n points_earned: 10\n points_possible: 10\n- question: 4\n points_earned: 3\n points_possible: 10\n- question: 5\n points_earned: 10\n points_possible: 10\n- question: 6\n points_earned: 0\n points_possible: 10\n- question: 7\n points_earned: 0\n points_possible: 10\n- question: 8\n points_earned: 3\n points_possible: 10\n- question: 9\n points_earned: 1\n points_possible: 10\n- question: 10\n points_earned: 0\n points_possible: 10\n- question: 11\n points_earned: 1\n points_possible: 10\n- question: 12\n points_earned: 6\n points_possible: 10\n- question: 13\n points_earned: 5\n points_possible: 10\ntotal_score: 92\npercentage: 67.34\ngrade: A\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 300
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate contract data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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:\ncontract_id,effective_date,parties,status,term_months,value\r\nCTR-218386,2026-01-02,\"[{\"\"name\"\": \"\"Gilmore, Harris and Avery\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Jefferson and Sons\"\", \"\"role\"\": \"\"p\",active,24,943840\r\nCTR-165927,2026-01-04,\"[{\"\"name\"\": \"\"Ellis, Nichols and Potter\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Morales-Smith\"\", \"\"role\"\": \"\"party_\",active,33,374883\r\nCTR-803232,2026-01-01,\"[{\"\"name\"\": \"\"Campos, Pierce and Murphy\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Frazier-Jordan\"\", \"\"role\"\": \"\"party\",pending,19,342893\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 209
} |
[
{
"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: 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:\ncourse_id: CRS-2652\ncode: JSD367\ntitle: Horizontal full-range open architecture 101\ninstructor: Michelle Ritter\ncredits: 3\nterm: Spring 2020\nschedule:\n- week: 1\n topic: week\n- week: 2\n topic: next\n- week: 3\n topic: paper\n- week: 4\n topic: about\n- week: 5\n topic: today\n- week: 6\n topic: six\n- week: 7\n topic: friend\n- week: 8\n topic: surface\n- week: 9\n topic: together\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 185
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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:\nnote_id: CN-5071105\npatient:\n mrn: MRN-878140\n age: 19\n gender: F\nencounter_date: '2026-01-04'\nchief_complaint: fever\nvitals:\n bp: 152/89\n hr: 107\n temp_f: 98.8\nassessment:\n- problem: diabetes\n icd10: K53\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 130
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result 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:\norder_date,panel,patient_mrn,result_id,results\r\n2026-01-05,CMP,MRN-198424,LAB-9877082,\"[{\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 99.1, \"\"unit\"\": \"\"g/dL\"\", \"\"flag\"\": \"\"high\"\"}, {\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 152.2, \"\"un\"\r\n2026-01-05,CMP,MRN-142544,LAB-3888813,\"[{\"\"test\"\": \"\"Glucose\"\", \"\"value\"\": 126.6, \"\"unit\"\": \"\"g/dL\"\", \"\"flag\"\": \"\"low\"\"}, {\"\"test\"\": \"\"Hemoglobin\"\", \"\"value\"\":\"\r\n2026-01-04,CMP,MRN-282262,LAB-7743037,\"[{\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 123.7, \"\"unit\"\": \"\"mg/dL\"\", \"\"flag\"\": \"\"high\"\"}, {\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 169.0, \"\"\"\r\n2026-01-05,Lipid,MRN-197425,LAB-7921937,\"[{\"\"test\"\": \"\"Hemoglobin\"\", \"\"value\"\": 82.6, \"\"unit\"\": \"\"g/dL\"\", \"\"flag\"\": \"\"normal\"\"}, {\"\"test\"\": \"\"Glucose\"\", \"\"value\"\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 250
} |
[
{
"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: 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:\ncontract_id = \"CTR-212036\"\neffective_date = \"2026-01-01\"\nterm_months = 38\nvalue = 221691\nstatus = \"pending\"\n[[parties]]\nname = \"Greene-Edwards\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Moore-Woods\"\nrole = \"party_b\"\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 125
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output product listing as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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:\nproduct_id: PROD-602506\nname: Diverse 5thgeneration monitoring\ncategory: electronics\nprice: 469.91\ncurrency: USD\nstock: 372\nis_available: true\nrating: 3.7\nreviews: 813\nspecs:\n weight_kg: 26.31\n dimensions: 49x82x12cm\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 132
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\n,EXP-625412,observational,106,443,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 68.03, \"\"endpoint\"\": 10.22, \"\"p_value\"\": 0.4955}, {\"\"metric\"\": \"\"efficacy\",Effect of call on sister\r\nsignificant,EXP-367995,observational,328,56,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 12.78, \"\"endpoint\"\": 86.94, \"\"p_value\"\": 0.313}, {\"\"metric\"\": \"\"efficac\",Effect of wait on agency\r\nnon-significant,EXP-864816,observational,297,919,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 29.58, \"\"endpoint\"\": 37.97, \"\"p_value\"\": 0.3369}, {\"\"metric\"\": \"\"efficacy\",Effect of within on doctor\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 244
} |
[
{
"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 \"paper_id\": \"arXiv:2020.93737\",\n \"title\": \"Pre-emptive incremental customer loyalty\",\n \"authors\": [\n {\n \"name\": \"Lindsay Reyes\",\n \"affiliation\": \"Alexander LLC\",\n \"email\": \"elambert@example.org\"\n },\n {\n \"name\": \"Katherine Scott\",\n \"affiliation\": \"Sanchez LLC\",\n \"email\": \"bschmidt@example.com\"\n },\n {\n \"name\": \"Patricia Richardson\",\n \"affiliation\": \"Schmidt, Phillips and Perez\",\n \"email\": \"michaelkirby@example.com\"\n }\n ],\n \"abstract\": \"Specific official couple reality development future treat they. Meet then order easy show to.\",\n \"keywords\": [\n \"somebody\",\n \"able\",\n \"even\",\n \"begin\"\n ],\n \"publication\": {\n \"venue\": \"Nature\",\n \"year\": 2024,\n \"doi\": \"10.3255/WtQx\"\n },\n \"citations\": 479,\n \"funding_source\": \"Abbott, Gonzalez and Smith\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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<research_paper>\n<paper_id>arXiv:2020.93737</paper_id>\n<title>Pre-emptive incremental customer loyalty</title>\n<authors>\n<name>Lindsay Reyes</name>\n<affiliation>Alexander LLC</affiliation>\n<email>elambert@example.org</email>\n</authors>\n<authors>\n<name>Katherine Scott</name>\n<affiliation>Sanchez LLC</affiliation>\n<email>bschmidt@example.com</email>\n</authors>\n<authors>\n<name>Patricia Richardson</name>\n<affiliation>Schmidt, Phillips and Perez</affiliation>\n<email>michaelkirby@example.com</email>\n</authors>\n<abstract>Specific official couple reality development future treat they. Meet then order easy show to.</abstract>\n<keywords>somebody</keywords>\n<keywords>able</keywords>\n<keywords>even</keywords>\n<keywords>begin</keywords>\n<publication>\n<venue>Nature</venue>\n<year>2024</year>\n<doi>10.3255/WtQx</doi>\n</publication>\n<citations>479</citations>\n<funding_source>Abbott, Gonzalez and Smith</funding_source>\n</research_paper>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 321
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output product listing as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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:\nproduct_id: PROD-877409\nname: Decentralized mobile framework\ncategory: electronics\nprice: 654.79\ncurrency: USD\nstock: 219\nis_available: true\nrating: 3.88\nreviews: 74\nspecs:\n weight_kg: 22.25\n dimensions: 82x76x89cm\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 132
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to YAML:\n{\n \"period\": \"November 2020\",\n \"total_revenue\": 2240268,\n \"units_sold\": 65559,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 3245532,\n \"growth\": 46.55\n },\n {\n \"name\": \"retail\",\n \"revenue\": 1159651,\n \"growth\": 18.88\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6794\",\n \"sales\": 277473\n },\n {\n \"sku\": \"SKU-6386\",\n \"sales\": 446824\n },\n {\n \"sku\": \"SKU-3299\",\n \"sales\": 143058\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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:\nperiod: November 2020\ntotal_revenue: 2240268\nunits_sold: 65559\nchannels:\n- name: wholesale\n revenue: 3245532\n growth: 46.55\n- name: retail\n revenue: 1159651\n growth: 18.88\ntop_products:\n- sku: SKU-6794\n sales: 277473\n- sku: SKU-6386\n sales: 446824\n- sku: SKU-3299\n sales: 143058\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 150
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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 \"note_id\": \"CN-9050287\",\n \"vitals\": {\n \"bp\": \"163/70\",\n \"hr\": 116,\n \"temp_f\": 98.5\n },\n \"chief_complaint\": \"chest pain\",\n \"encounter_date\": \"2026-01-05\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 121
} |
[
{
"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 lab result."
},
{
"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-6952132\"\npatient_mrn = \"MRN-506756\"\norder_date = \"2026-01-01\"\npanel = \"CBC\"\n[[results]]\ntest = \"Glucose\"\nvalue = 50.5\nunit = \"mg/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 54.6\nunit = \"g/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 80.5\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 76.6\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 133.2\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 167.4\nunit = \"mg/dL\"\nflag = \"low\"\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 199
} |
[
{
"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 \"result_id\": \"LAB-6952132\",\n \"patient_mrn\": \"MRN-506756\",\n \"order_date\": \"2026-01-01\",\n \"panel\": \"CBC\",\n \"results\": [\n {\n \"test\": \"Glucose\",\n \"value\": 50.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 54.6,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 80.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 76.6,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 133.2,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 167.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result 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<lab_result>\n<result_id>LAB-6952132</result_id>\n<patient_mrn>MRN-506756</patient_mrn>\n<order_date>2026-01-01</order_date>\n<panel>CBC</panel>\n<results>\n<test>Glucose</test>\n<value>50.5</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>54.6</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>80.5</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>76.6</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>133.2</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>167.4</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n</lab_result>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "conversion",
"estimated_tokens": 269
} |
[
{
"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 prescription."
},
{
"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-2110944\npatient_mrn: MRN-267033\nprescriber: Paul Ellis\ndate: '2026-01-02'\nmedications:\n- name: Atorvastatin\n dosage: 20mg\n frequency: TID\n quantity: 30\n- name: Atorvastatin\n dosage: 20mg\n frequency: BID\n quantity: 90\n- name: Lisinopril\n dosage: 10mg\n frequency: daily\n quantity: 60\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 152
} |
[
{
"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 XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-723468</experiment_id>\n<title>Effect of thing on action</title>\n<methodology>\n<design>RCT</design>\n<sample_size>202</sample_size>\n<duration_days>356</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>12.99</baseline>\n<endpoint>34.4</endpoint>\n<p_value>0.3458</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>92.51</baseline>\n<endpoint>36.28</endpoint>\n<p_value>0.1764</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>21.83</baseline>\n<endpoint>83.74</endpoint>\n<p_value>0.306</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: 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 \"experiment_id\": \"EXP-723468\",\n \"title\": \"Effect of thing on action\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 202,\n \"duration_days\": 356\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 12.99,\n \"endpoint\": 34.4,\n \"p_value\": 0.3458\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 92.51,\n \"endpoint\": 36.28,\n \"p_value\": 0.1764\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 21.83,\n \"endpoint\": 83.74,\n \"p_value\": 0.306\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 221
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate financial report data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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 \"company\": \"Lewis PLC\",\n \"ticker\": \"GBMW\",\n \"quarter\": \"Q3 2022\",\n \"revenue\": 96366649,\n \"expenses\": 22348545,\n \"net_income\": 10822841,\n \"eps\": 7.82,\n \"metrics\": {\n \"profit_margin\": 9.38,\n \"roe\": 19.54\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 134
} |
[
{
"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 sales analytics."
},
{
"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 = \"May 2020\"\ntotal_revenue = 1974408\nunits_sold = 62373\n[[channels]]\nname = \"retail\"\nrevenue = 3281260\ngrowth = 46.14\n\n[[channels]]\nname = \"wholesale\"\nrevenue = 3133363\ngrowth = 43.03\n\n[[top_products]]\nsku = \"SKU-8258\"\nsales = 375026\n\n[[top_products]]\nsku = \"SKU-2687\"\nsales = 345567\n\n[[top_products]]\nsku = \"SKU-9980\"\nsales = 457570\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 160
} |
[
{
"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 prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription 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:\ndate: '2026-01-04'\npatient_mrn: MRN-962030\nprescriber: Brandon Tucker\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 95
} |
[
{
"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: 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:\nrx_id: RX-3631259\npatient_mrn: MRN-600950\nprescriber: Joshua Allen\ndate: '2026-01-03'\nmedications:\n- name: Lisinopril\n dosage: 5mg\n frequency: daily\n quantity: 90\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\nassessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type\r\nASMT-391811,,CRS-7911,,2026-01-02,C,,,,,64.45,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 1, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 1, \"\"po\",STU-626330,,,84,quiz\r\n,SZX330,CRS-4650,3,,,40,30,30,Anthony Flores,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"return\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"several\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"with\"\"}, {\"\"we\",,,Spring 2021,Reverse-engineered national pricing structure 101,,\r\n,EWX438,CRS-3957,3,,,40,30,30,Wesley Hendrix,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"present\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"north\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"throw\"\"}, {\"\"we\",,,Fall 2024,Adaptive bi-directional synergy 101,,\r\n,ZKQ434,CRS-9166,4,,,40,30,30,Lindsey Ingram,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"order\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"tough\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"during\"\"}, {\"\"wee\",,,Spring 2024,Implemented next generation solution 101,,\r\n,BBU189,CRS-8641,3,,,40,30,30,Robin Arroyo,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"song\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"cultural\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"political\"\"}, \",,,Fall 2021,Optimized systematic focus group 101,,\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 391
} |
[
{
"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 YAML to JSON:\nperiod: May 2021\ntotal_revenue: 5805544\nunits_sold: 31472\nchannels:\n- name: wholesale\n revenue: 1100052\n growth: -3.92\n- name: online\n revenue: 1652141\n growth: 2.79\ntop_products:\n- sku: SKU-4912\n sales: 74292\n- sku: SKU-1590\n sales: 50210\n- sku: SKU-8419\n sales: 321973\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from YAML 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\": \"May 2021\",\n \"total_revenue\": 5805544,\n \"units_sold\": 31472,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 1100052,\n \"growth\": -3.92\n },\n {\n \"name\": \"online\",\n \"revenue\": 1652141,\n \"growth\": 2.79\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-4912\",\n \"sales\": 74292\n },\n {\n \"sku\": \"SKU-1590\",\n \"sales\": 50210\n },\n {\n \"sku\": \"SKU-8419\",\n \"sales\": 321973\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output error log as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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:\nstack_trace = [ \"at play.py:21\", \"at space.py:166\", \"at public.py:493\", \"at government.py:462\",]\nerror_id = \"dece4525-b43a-42c0-bd19-590427aeb5ca\"\nservice = \"wrongService\"\nmessage = \"Too daughter color draw role.\"\n\n[context]\nuser_id = \"13bdf80c-dec5-4389-9c68-b3142ee30270\"\nrequest_id = \"585587b7-59eb-45b4-83bd-d58fe462800c\"\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 155
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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 \"experiment_id\": \"EXP-460532\",\n \"title\": \"Effect of data on kid\",\n \"methodology\": {\n \"design\": \"observational\",\n \"sample_size\": 482,\n \"duration_days\": 320\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 32.76,\n \"endpoint\": 19.95,\n \"p_value\": 0.1938\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 34.66,\n \"endpoint\": 72.26,\n \"p_value\": 0.255\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 192
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate customer review data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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<customer_review>\n<rating>2</rating>\n<date>2026-01-01</date>\n<helpful_votes>73</helpful_votes>\n<title>News production decide today.</title>\n<verified_purchase>False</verified_purchase>\n</customer_review>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 139
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate course syllabus data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nNGM306,CRS-6754,3,40,30,30,Shannon Gonzalez,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"much\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"little\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"station\"\"}, {\"\"we\",Spring 2020,User-centric bottom-line Local Area Network 101\r\nNJR262,CRS-8487,3,40,30,30,Jacob Powell,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"space\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"likely\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"by\"\"}, {\"\"week\"\":\",Spring 2023,Reduced heuristic budgetary management 101\r\nCHR332,CRS-8823,3,40,30,30,Kyle Rose,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"soon\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"ahead\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"reveal\"\"}, {\"\"week\",Spring 2021,Synchronized scalable framework 101\r\nAWL336,CRS-4993,3,40,30,30,Kara Cline,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"they\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"since\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"pay\"\"}, {\"\"week\"\": \",Spring 2020,Versatile non-volatile artificial intelligence 101\r\nSKB403,CRS-7550,4,40,30,30,Jason Wright,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"sense\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"catch\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"Republican\"\"}, {\",Spring 2023,Synergistic disintermediate instruction set 101\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 378
} |
[
{
"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 \"note_id\": \"CN-4150804\",\n \"patient\": {\n \"mrn\": \"MRN-300983\",\n \"age\": 74,\n \"gender\": \"M\"\n },\n \"encounter_date\": \"2026-01-03\",\n \"chief_complaint\": \"chest pain\",\n \"vitals\": {\n \"bp\": \"105/60\",\n \"hr\": 75,\n \"temp_f\": 98.4\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J93\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J76\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note 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<clinical_note>\n<note_id>CN-4150804</note_id>\n<patient>\n<mrn>MRN-300983</mrn>\n<age>74</age>\n<gender>M</gender>\n</patient>\n<encounter_date>2026-01-03</encounter_date>\n<chief_complaint>chest pain</chief_complaint>\n<vitals>\n<bp>105/60</bp>\n<hr>75</hr>\n<temp_f>98.4</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>J93</icd10>\n</assessment>\n<assessment>\n<problem>hypertension</problem>\n<icd10>J76</icd10>\n</assessment>\n</clinical_note>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 201
} |
[
{
"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 YAML to JSON:\nexperiment_id: EXP-974476\ntitle: Effect of card on political\nmethodology:\n design: cohort\n sample_size: 185\n duration_days: 133\nresults:\n- metric: safety\n baseline: 81.86\n endpoint: 95.41\n p_value: 0.4221\n- metric: efficacy\n baseline: 28.31\n endpoint: 51.25\n p_value: 0.3164\n- metric: efficacy\n baseline: 74.07\n endpoint: 10.16\n p_value: 0.1195\n- metric: safety\n baseline: 73.28\n endpoint: 70.63\n p_value: 0.073\nconclusion: significant\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from YAML 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 \"experiment_id\": \"EXP-974476\",\n \"title\": \"Effect of card on political\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 185,\n \"duration_days\": 133\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 81.86,\n \"endpoint\": 95.41,\n \"p_value\": 0.4221\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 28.31,\n \"endpoint\": 51.25,\n \"p_value\": 0.3164\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 74.07,\n \"endpoint\": 10.16,\n \"p_value\": 0.1195\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 73.28,\n \"endpoint\": 70.63,\n \"p_value\": 0.073\n }\n ],\n \"conclusion\": \"significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 250
} |
[
{
"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 \"company\": \"Hunt, Byrd and Taylor\",\n \"ticker\": \"WJGR\",\n \"quarter\": \"Q3 2020\",\n \"revenue\": 9059648,\n \"expenses\": 70825887,\n \"net_income\": 7626987,\n \"eps\": 2.68,\n \"metrics\": {\n \"profit_margin\": 6.55,\n \"roe\": 5.91\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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<financial_report>\n<company>Hunt, Byrd and Taylor</company>\n<ticker>WJGR</ticker>\n<quarter>Q3 2020</quarter>\n<revenue>9059648</revenue>\n<expenses>70825887</expenses>\n<net_income>7626987</net_income>\n<eps>2.68</eps>\n<metrics>\n<profit_margin>6.55</profit_margin>\n<roe>5.91</roe>\n</metrics>\n</financial_report>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 166
} |
[
{
"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: 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:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\n\"Craig, Clark and Kent\",5.77,34396688,10.65,13.61,15229291,Q2 2024,6156154,PIOR\r\n\"Johnson, Bryant and Rivera\",2.21,14111904,8.34,24.72,8622513,Q4 2022,93763270,SMEO\r\n\"Garcia, Haynes and Garza\",4.88,35384135,15.53,11.78,5883171,Q2 2022,75504563,FLVX\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 162
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>User-friendly analyzing definition API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</upon>\n<get>\n<summary>Can although economy once indicate reflect.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param2</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//upon>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 243
} |
[
{
"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 clinical note."
},
{
"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-2813545\npatient:\n mrn: MRN-361411\n age: 61\n gender: M\nencounter_date: '2026-01-01'\nchief_complaint: chest pain\nvitals:\n bp: 126/99\n hr: 78\n temp_f: 102.4\nassessment:\n- problem: diabetes\n icd10: K41\n- problem: hypertension\n icd10: K90\n- problem: diabetes\n icd10: J65\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 149
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result 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<lab_result>\n<result_id>LAB-3220917</result_id>\n<patient_mrn>MRN-847879</patient_mrn>\n<order_date>2026-01-01</order_date>\n<panel>CBC</panel>\n<results>\n<test>Hemoglobin</test>\n<value>77.2</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>173.8</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>177.0</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>171.8</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>77.3</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>167.6</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n</lab_result>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 272
} |
[
{
"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 prescription."
},
{
"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-5635817\",\n \"patient_mrn\": \"MRN-524932\",\n \"prescriber\": \"Thomas Olson\",\n \"date\": \"2026-01-03\",\n \"medications\": [\n {\n \"name\": \"Metformin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n },\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 196
} |
[
{
"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: Lewis PLC\nticker: GBMW\nquarter: Q3 2022\nrevenue: 96366649\nexpenses: 22348545\nnet_income: 10822841\neps: 7.82\nmetrics:\n profit_margin: 9.38\n roe: 19.54\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 118
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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<student_assessment>\n<date>2026-01-02</date>\n<grade>C</grade>\n<course_id>CRS-4587</course_id>\n<total_score>78</total_score>\n<assessment_id>ASMT-811902</assessment_id>\n</student_assessment>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 136
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate social media post data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in 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. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,content,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,timestamp,title,username\r\n,,,Pass south detail product provide. Recently board lawyer view about discuss most. Sense decision sor,,,,,,,2026-01-07T01:26:12.314571,,leematthew\r\nProbably within team design have turn. Instead change opportunity ok.,\"[{\"\"name\"\": \"\"Michele Lopez\"\", \"\"affiliation\"\": \"\"Orr-Burgess\"\", \"\"email\"\": \"\"smithdiana@example.org\"\"}, {\"\"name\"\"\",294,,Smith LLC,\"[\"\"themselves\"\", \"\"live\"\", \"\"hour\"\"]\",arXiv:2024.11073,10.8307/PvTb,Science,2020,,Optimized eco-centric algorithm,\r\nHusband prevent significant little. Defense put must which yeah character carry. Expect clear provid,\"[{\"\"name\"\": \"\"Jason Butler\"\", \"\"affiliation\"\": \"\"Snyder Ltd\"\", \"\"email\"\": \"\"colemansarah@example.net\"\"}, {\"\"name\"\"\",46,,Jimenez-Austin,\"[\"\"across\"\", \"\"change\"\", \"\"cut\"\"]\",arXiv:2024.41067,10.6329/YzwA,Nature,2021,,Function-based uniform initiative,\r\nMiss billion off level. Finally peace perhaps us.,\"[{\"\"name\"\": \"\"Angela Neal\"\", \"\"affiliation\"\": \"\"Anderson-Mills\"\", \"\"email\"\": \"\"arielfreeman@example.net\"\"}, {\"\"na\",425,,None,\"[\"\"live\"\", \"\"they\"\", \"\"mouth\"\"]\",arXiv:2024.41878,10.1909/dYjT,Nature,2022,,User-friendly responsive website,\r\nState want current station couple. Wonder month talk century. Yes billion huge.,\"[{\"\"name\"\": \"\"Rose Melendez\"\", \"\"affiliation\"\": \"\"Fitzpatrick, Jones and Sherman\"\", \"\"email\"\": \"\"curtischelsey@\",478,,Payne-James,\"[\"\"official\"\", \"\"you\"\", \"\"bad\"\"]\",arXiv:2024.65770,10.5095/KvpB,Cell,2022,,Adaptive bi-directional ability,\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 472
} |
[
{
"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 \"parties\": [\n {\n \"name\": \"Brown, Richards and Sparks\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Saunders-Martinez\",\n \"role\": \"party_b\"\n }\n ],\n \"value\": 719358,\n \"effective_date\": \"2026-01-01\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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<contract>\n<parties>\n<name>Brown, Richards and Sparks</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Saunders-Martinez</name>\n<role>party_b</role>\n</parties>\n<value>719358</value>\n<effective_date>2026-01-01</effective_date>\n</contract>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 148
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.