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": "Generate contract data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id = \"CTR-640570\"\neffective_date = \"2026-01-06\"\nterm_months = 52\nvalue = 450714\nstatus = \"pending\"\n[[parties]]\nname = \"Mitchell-Clark\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Simmons-Marquez\"\nrole = \"party_b\""
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 127
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output contract as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in YAML\n2. Complexity: 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:\ncontract_id: CTR-370819\nparties:\n- name: Stewart, Thompson and Rogers\n role: party_a\n- name: Jackson, Griffin and Flowers\n role: party_b\neffective_date: '2026-01-01'\nterm_months: 13\nvalue: 109351\nstatus: active"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 129
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate course syllabus data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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:\ncourse_id = \"CRS-4513\"\ncode = \"NEE477\"\ntitle = \"Exclusive bottom-line artificial intelligence 101\"\ninstructor = \"Jaime Roman\"\ncredits = 3\nterm = \"Spring 2022\"\n[[schedule]]\nweek = 1\ntopic = \"marriage\"\n\n[[schedule]]\nweek = 2\ntopic = \"wonder\"\n\n[[schedule]]\nweek = 3\ntopic = \"system\"\n\n[[schedule]]\nweek = 4\ntopic = \"order\"\n\n[[schedule]]\nweek = 5\ntopic = \"very\"\n\n[[schedule]]\nweek = 6\ntopic = \"laugh\"\n\n[[schedule]]\nweek = 7\ntopic = \"practice\"\n\n[[schedule]]\nweek = 8\ntopic = \"sister\"\n\n[[schedule]]\nweek = 9\ntopic = \"join\"\n\n[[schedule]]\nweek = 10\ntopic = \"expect\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 225
}
|
[
{
"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<clinical_note>\n<note_id>CN-6224145</note_id>\n<patient>\n<mrn>MRN-560569</mrn>\n<age>88</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>119/73</bp>\n<hr>63</hr>\n<temp_f>100.0</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>I32</icd10>\n</assessment>\n</clinical_note>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"note_id\": \"CN-6224145\",\n \"patient\": {\n \"mrn\": \"MRN-560569\",\n \"age\": 88,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-04\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"119/73\",\n \"hr\": 63,\n \"temp_f\": 100.0\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"I32\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"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": "Reformat the data below from JSON to XML:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Distributed high-level website API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/next\": {\n \"get\": {\n \"summary\": \"Movie my movie common adult.\",\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 \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Distributed high-level website API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</next>\n<get>\n<summary>Movie my movie common adult.</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>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//next>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 224
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this CSV data into XML format:\nabstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold\r\n,,\"[{\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 3952303, \"\"growth\"\": 2.75}, {\"\"name\"\": \"\"retail\"\", \"\"revenue\"\": 3970412, \"\"gro\",,,,,March 2024,,,,,\"[{\"\"sku\"\": \"\"SKU-2514\"\", \"\"sales\"\": 485558}, {\"\"sku\"\": \"\"SKU-5241\"\", \"\"sales\"\": 142515}, {\"\"sku\"\": \"\"SKU-4600\"\", \"\"sa\",2433324,8686\r\nAdult house daughter but short serious. Agree hand career mean.,\"[{\"\"name\"\": \"\"Steven Fernandez\"\", \"\"affiliation\"\": \"\"Gutierrez-Warren\"\", \"\"email\"\": \"\"qgibson@example.com\"\"}, {\"\"\",,107,\"Holland, Garcia and Owens\",\"[\"\"security\"\", \"\"present\"\", \"\"share\"\", \"\"yes\"\", \"\"heavy\"\"]\",arXiv:2021.72507,,10.3146/DNoC,Nature,2022,Networked needs-based approach,,,\r\nAbove health management board institution. Sell since while. Improve bit want shoulder course better,\"[{\"\"name\"\": \"\"James Petersen\"\", \"\"affiliation\"\": \"\"Arnold-Smith\"\", \"\"email\"\": \"\"brandon75@example.org\"\"}, {\"\"name\",,170,\"Rodriguez, Gonzales and Decker\",\"[\"\"offer\"\", \"\"team\"\", \"\"item\"\"]\",arXiv:2022.30243,,10.5369/wkrw,Cell,2022,Devolved asynchronous alliance,,,\r\nStage five grow somebody. Others simply firm writer boy central culture. Pass production stay actual,\"[{\"\"name\"\": \"\"Adrienne Edwards\"\", \"\"affiliation\"\": \"\"Smith-Hernandez\"\", \"\"email\"\": \"\"carlanixon@example.com\"\"}, \",,121,Zimmerman PLC,\"[\"\"teacher\"\", \"\"top\"\", \"\"exactly\"\"]\",arXiv:2022.77777,,10.2791/oMYv,Science,2021,Digitized value-added alliance,,,\r\nGuy decide general. Partner avoid pressure ten bit beat white blood.,\"[{\"\"name\"\": \"\"Yolanda Wells\"\", \"\"affiliation\"\": \"\"Stewart, Garcia and Chavez\"\", \"\"email\"\": \"\"stevensonrenee@exa\",,211,White-Collins,\"[\"\"language\"\", \"\"article\"\", \"\"character\"\", \"\"argue\"\"]\",arXiv:2021.35384,,10.9321/SyHJ,Science,2022,Synchronized fault-tolerant forecast,,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from CSV 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<sales_analytics>\n<period>March 2024</period>\n<total_revenue>2433324</total_revenue>\n<units_sold>8686</units_sold>\n<channels>\n<name>online</name>\n<revenue>3952303</revenue>\n<growth>2.75</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>3970412</revenue>\n<growth>12.57</growth>\n</channels>\n<top_products>\n<sku>SKU-2514</sku>\n<sales>485558</sales>\n</top_products>\n<top_products>\n<sku>SKU-5241</sku>\n<sales>142515</sales>\n</top_products>\n<top_products>\n<sku>SKU-4600</sku>\n<sales>420300</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 223
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate social media post data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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 \"post_id\": \"POST-90196326\",\n \"platform\": \"facebook\",\n \"user_id\": \"146c178d-e548-4357-8cd4-e8464cea2f9b\",\n \"username\": \"kevincunningham\",\n \"content\": \"Three would identify method across operation opportunity.\\nWhat realize number. Country perform simple team player. Improve order east mother news magazine trade.\\nCentral thus simple thousand morning.\",\n \"timestamp\": \"2026-01-07T13:51:26.698310\",\n \"hashtags\": [\n \"#pay\",\n \"#keep\"\n ],\n \"engagement\": {\n \"likes\": 458,\n \"shares\": 383,\n \"comments\": 63\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 211
}
|
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\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-549878,,CRS-6692,,2026-01-01,C,,,,,54.38,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 7, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 1, \"\"po\",STU-264168,,,70,assignment\r\n,KQK318,CRS-7446,4,,,40,30,30,Gerald Morris,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"economic\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"thing\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"one\"\"}, {\"\"wee\",,,Spring 2024,Mandatory real-time capability 101,,\r\n,NPQ465,CRS-7705,4,,,40,30,30,Justin Gibson,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"black\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"sign\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"table\"\"}, {\"\"week\"\"\",,,Spring 2020,User-friendly asynchronous database 101,,"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 279
}
|
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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 \"assessment_id\": \"ASMT-946690\",\n \"student_id\": \"STU-268675\",\n \"course_id\": \"CRS-1216\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-01\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 2,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 81,\n \"percentage\": 50.49,\n \"grade\": \"B\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 398
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"content\": \"Range condition class leader wrong subject wait. Stop we prevent particular front method. Force item executive employee green large house nation. General doctor material rule head event.\\nOne will dog chance. Order away music seem director put upon. Find boy again direction four.\",\n \"article_id\": \"ART-9628131\",\n \"headline\": \"Re-contextualized logistical paradigm\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<content>Range condition class leader wrong subject wait. Stop we prevent particular front method. Force item executive employee green large house nation. General doctor material rule head event.\nOne will dog chance. Order away music seem director put upon. Find boy again direction four.</content>\n<article_id>ART-9628131</article_id>\n<headline>Re-contextualized logistical paradigm</headline>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 195
}
|
[
{
"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 = \"March 2022\"\ntotal_revenue = 6503980\nunits_sold = 7670\n[[channels]]\nname = \"retail\"\nrevenue = 3279241\ngrowth = 22.76\n\n[[channels]]\nname = \"wholesale\"\nrevenue = 1469640\ngrowth = 16.07\n\n[[top_products]]\nsku = \"SKU-8081\"\nsales = 71747\n\n[[top_products]]\nsku = \"SKU-8211\"\nsales = 475825\n\n[[top_products]]\nsku = \"SKU-4565\"\nsales = 485553"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 160
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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<product_listing>\n<product_id>PROD-308726</product_id>\n<name>Cross-platform client-server attitude</name>\n<category>electronics</category>\n<price>875.12</price>\n<currency>USD</currency>\n<stock>161</stock>\n<is_available>True</is_available>\n<rating>1.18</rating>\n<reviews>705</reviews>\n<specs>\n<weight_kg>37.34</weight_kg>\n<dimensions>78x81x41cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 183
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate research paper data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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 \"paper_id\": \"arXiv:2020.69453\",\n \"title\": \"Assimilated needs-based portal\",\n \"authors\": [\n {\n \"name\": \"Evan Reed\",\n \"affiliation\": \"Orr, Wheeler and Johnson\",\n \"email\": \"cheryl05@example.net\"\n },\n {\n \"name\": \"Amanda Mcmahon\",\n \"affiliation\": \"Maxwell-Price\",\n \"email\": \"mbowen@example.org\"\n },\n {\n \"name\": \"Angel Vasquez\",\n \"affiliation\": \"Melendez, Osborne and Harris\",\n \"email\": \"timothysutton@example.com\"\n }\n ],\n \"abstract\": \"Economy instead thank kitchen. For pattern he purpose strong goal challenge.\",\n \"keywords\": [\n \"power\",\n \"main\",\n \"light\",\n \"form\",\n \"system\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2024,\n \"doi\": \"10.9550/gbOm\"\n },\n \"citations\": 115,\n \"funding_source\": null\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 277
}
|
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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:\nnet_income = 4233102\ncompany = \"Blackwell, Simpson and Pace\"\neps = 0.79\nexpenses = 41343491\n\n[metrics]\nprofit_margin = 14.29\nroe = 18.28"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 110
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Transform this YAML data into TOML format:\nreviews: 730\ncategory: books\nstock: 824\nis_available: true\nspecs:\n weight_kg: 7.36\n dimensions: 46x21x76cm\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from YAML to TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nreviews = 730\ncategory = \"books\"\nstock = 824\nis_available = true\n\n[specs]\nweight_kg = 7.36\ndimensions = \"46x21x76cm\""
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 106
}
|
[
{
"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 \"period\": \"November 2022\",\n \"total_revenue\": 9138741,\n \"units_sold\": 89798,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 1234153,\n \"growth\": 40.64\n },\n {\n \"name\": \"online\",\n \"revenue\": 991509,\n \"growth\": -4.15\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-9585\",\n \"sales\": 30234\n },\n {\n \"sku\": \"SKU-8072\",\n \"sales\": 57362\n },\n {\n \"sku\": \"SKU-4011\",\n \"sales\": 249730\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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<sales_analytics>\n<period>November 2022</period>\n<total_revenue>9138741</total_revenue>\n<units_sold>89798</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>1234153</revenue>\n<growth>40.64</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>991509</revenue>\n<growth>-4.15</growth>\n</channels>\n<top_products>\n<sku>SKU-9585</sku>\n<sales>30234</sales>\n</top_products>\n<top_products>\n<sku>SKU-8072</sku>\n<sales>57362</sales>\n</top_products>\n<top_products>\n<sku>SKU-4011</sku>\n<sales>249730</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"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": "Generate contract data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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,effective_date,funding_source,keywords,paper_id,parties,publication_doi,publication_venue,publication_year,term_months,title,value\r\n,,,2026-01-05,,,,\"[{\"\"name\"\": \"\"Hart-Villanueva\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Roberts Ltd\"\", \"\"role\"\": \"\"party_b\"\"}]\",,,,33,,95653\r\n\"Their tend build gas spring blood man short.\nListen perhaps institution career case.\nReach left prof\",\"[{\"\"name\"\": \"\"Shannon Lee\"\", \"\"affiliation\"\": \"\"Johns-Parker\"\", \"\"email\"\": \"\"marquezapril@example.org\"\"}, {\"\"name\",1,,Clark PLC,\"[\"\"base\"\", \"\"week\"\", \"\"soldier\"\", \"\"go\"\", \"\"policy\"\"]\",arXiv:2023.75547,,10.4080/LbDF,Nature,2023,,Distributed multi-state standardization,\r\n\"Fire for worry night natural. Table people possible appear.\nRed want fall fill. Election somebody tw\",\"[{\"\"name\"\": \"\"Denise West\"\", \"\"affiliation\"\": \"\"Bonilla PLC\"\", \"\"email\"\": \"\"williamsmichael@example.net\"\"}, {\"\"na\",227,,None,\"[\"\"glass\"\", \"\"value\"\", \"\"me\"\", \"\"its\"\"]\",arXiv:2023.46555,,10.3610/ujqA,Cell,2020,,Ergonomic executive Internet solution,\r\nDifficult turn morning message TV job. Relationship floor tonight politics whether lot edge. Affect ,\"[{\"\"name\"\": \"\"Barbara Lewis\"\", \"\"affiliation\"\": \"\"Robles-Mcfarland\"\", \"\"email\"\": \"\"callahanamy@example.net\"\"}, {\",31,,None,\"[\"\"team\"\", \"\"each\"\", \"\"great\"\", \"\"day\"\"]\",arXiv:2024.30502,,10.1960/MuGR,Nature,2024,,Ergonomic scalable architecture,"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 420
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output customer review as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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:\nverified_purchase: true\ntitle: Country especially hand.\nreview_id: REV-4835597\nproduct_id: PROD-713270"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 104
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. , then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate student assessment data in JSON format."
},
{
"role": "assistant",
"content": "{\n \"total_score\": 97,\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 4,\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\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 5,\n \"points_possible\": 10\n }\n ],\n \"percentage\": 78.32,\n \"course_id\": \"CRS-4089\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 345
}
|
[
{
"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<sales_analytics>\n<period>June 2024</period>\n<total_revenue>5319249</total_revenue>\n<units_sold>96009</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>941227</revenue>\n<growth>26.4</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>937409</revenue>\n<growth>30.07</growth>\n</channels>\n<top_products>\n<sku>SKU-2900</sku>\n<sales>81858</sales>\n</top_products>\n<top_products>\n<sku>SKU-8266</sku>\n<sales>123988</sales>\n</top_products>\n<top_products>\n<sku>SKU-9969</sku>\n<sales>32400</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"period\": \"June 2024\",\n \"total_revenue\": 5319249,\n \"units_sold\": 96009,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 941227,\n \"growth\": 26.4\n },\n {\n \"name\": \"retail\",\n \"revenue\": 937409,\n \"growth\": 30.07\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-2900\",\n \"sales\": 81858\n },\n {\n \"sku\": \"SKU-8266\",\n \"sales\": 123988\n },\n {\n \"sku\": \"SKU-9969\",\n \"sales\": 32400\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"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 \"assessment_id\": \"ASMT-871992\",\n \"student_id\": \"STU-916232\",\n \"course_id\": \"CRS-5865\",\n \"type\": \"quiz\",\n \"date\": \"2026-01-05\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 1,\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\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 5,\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\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 5,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 83,\n \"percentage\": 70.57,\n \"grade\": \"B\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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<student_assessment>\n<assessment_id>ASMT-871992</assessment_id>\n<student_id>STU-916232</student_id>\n<course_id>CRS-5865</course_id>\n<type>quiz</type>\n<date>2026-01-05</date>\n<scores>\n<question>1</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>11</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>83</total_score>\n<percentage>70.57</percentage>\n<grade>B</grade>\n</student_assessment>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 469
}
|
[
{
"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 TOML to YAML:\ncontract_id = \"CTR-640570\"\neffective_date = \"2026-01-06\"\nterm_months = 52\nvalue = 450714\nstatus = \"pending\"\n[[parties]]\nname = \"Mitchell-Clark\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Simmons-Marquez\"\nrole = \"party_b\"\n\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from TOML 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:\ncontract_id: CTR-640570\nparties:\n- name: Mitchell-Clark\n role: party_a\n- name: Simmons-Marquez\n role: party_b\neffective_date: '2026-01-06'\nterm_months: 52\nvalue: 450714\nstatus: pending"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 124
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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<product_listing>\n<product_id>PROD-942707</product_id>\n<name>Organic demand-driven installation</name>\n<category>books</category>\n<price>698.66</price>\n<currency>USD</currency>\n<stock>819</stock>\n<is_available>True</is_available>\n<rating>4.45</rating>\n<reviews>103</reviews>\n<specs>\n<weight_kg>32.63</weight_kg>\n<dimensions>66x30x83cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 180
}
|
[
{
"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 \"course_id\": \"CRS-8328\",\n \"code\": \"QKE428\",\n \"title\": \"Decentralized content-based leverage 101\",\n \"instructor\": \"Sarah Simon\",\n \"credits\": 3,\n \"term\": \"Fall 2022\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"whole\"\n },\n {\n \"week\": 2,\n \"topic\": \"table\"\n },\n {\n \"week\": 3,\n \"topic\": \"determine\"\n },\n {\n \"week\": 4,\n \"topic\": \"evening\"\n },\n {\n \"week\": 5,\n \"topic\": \"once\"\n },\n {\n \"week\": 6,\n \"topic\": \"some\"\n },\n {\n \"week\": 7,\n \"topic\": \"themselves\"\n },\n {\n \"week\": 8,\n \"topic\": \"table\"\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 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<course_syllabus>\n<course_id>CRS-8328</course_id>\nQKE428\n<title>Decentralized content-based leverage 101</title>\n<instructor>Sarah Simon</instructor>\n<credits>3</credits>\n<term>Fall 2022</term>\n<schedule>\n<week>1</week>\n<topic>whole</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>table</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>determine</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>evening</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>once</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>some</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>themselves</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>table</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 286
}
|
[
{
"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 \"period\": \"June 2021\",\n \"total_revenue\": 4317671,\n \"units_sold\": 11582,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 2780960,\n \"growth\": 22.76\n },\n {\n \"name\": \"retail\",\n \"revenue\": 4140341,\n \"growth\": -9.84\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-8636\",\n \"sales\": 261407\n },\n {\n \"sku\": \"SKU-9950\",\n \"sales\": 107242\n },\n {\n \"sku\": \"SKU-8311\",\n \"sales\": 494004\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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<sales_analytics>\n<period>June 2021</period>\n<total_revenue>4317671</total_revenue>\n<units_sold>11582</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>2780960</revenue>\n<growth>22.76</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>4140341</revenue>\n<growth>-9.84</growth>\n</channels>\n<top_products>\n<sku>SKU-8636</sku>\n<sales>261407</sales>\n</top_products>\n<top_products>\n<sku>SKU-9950</sku>\n<sales>107242</sales>\n</top_products>\n<top_products>\n<sku>SKU-8311</sku>\n<sales>494004</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 223
}
|
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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 \"post_id\": \"POST-66277640\",\n \"platform\": \"instagram\",\n \"user_id\": \"7e83a029-16e2-49ad-a855-906c882abe46\",\n \"username\": \"reynoldstaylor\",\n \"content\": \"Thousand book animal myself wear beautiful. Room rock couple reality her.\\nJoin town travel agency value improve way. Heavy late science mind develop consider ability.\",\n \"timestamp\": \"2026-01-07T13:51:26.676406\",\n \"hashtags\": [\n \"#case\",\n \"#along\",\n \"#only\",\n \"#have\"\n ],\n \"engagement\": {\n \"likes\": 9942,\n \"shares\": 119,\n \"comments\": 368\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 210
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output transaction record as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ntax = 39.55\ntotal = 1865.58\ncustomer_id = \"bf96f80b-072c-4f04-82b0-c235c01681a8\"\n[[items]]\nsku = \"SKU-71565\"\nqty = 1\nprice = 387.38\n\n[[items]]\nsku = \"SKU-23891\"\nqty = 1\nprice = 432.74\n\n[[items]]\nsku = \"SKU-77840\"\nqty = 1\nprice = 463.12\n\n[[items]]\nsku = \"SKU-27496\"\nqty = 3\nprice = 295.3"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 148
}
|
[
{
"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 error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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:\nerror_id = \"234c0781-6e40-4e46-8b0d-ad1b39309eb0\"\ntimestamp = \"2026-01-07T13:51:25.659911\"\nlevel = \"WARNING\"\nservice = \"beyondService\"\nmessage = \"Section material entire top community.\"\nstack_trace = [ \"at reason.py:320\", \"at always.py:365\", \"at red.py:27\",]\n\n[context]\nuser_id = \"6765bd92-f82e-426f-a383-fa0a088a0752\"\nrequest_id = \"4ccfb0b5-8185-4d26-902a-0379b3534400\""
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 166
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. , then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this TOML data into YAML format:\ncompany = \"Ortega-Owens\"\nticker = \"YLLB\"\nquarter = \"Q3 2022\"\nrevenue = 37598920\nexpenses = 44591506\nnet_income = 3197580\neps = 1.51\n\n[metrics]\nprofit_margin = 5.54\nroe = 6.32\n"
},
{
"role": "assistant",
"content": "company: Ortega-Owens\nticker: YLLB\nquarter: Q3 2022\nrevenue: 37598920\nexpenses: 44591506\nnet_income: 3197580\neps: 1.51\nmetrics:\n profit_margin: 5.54\n roe: 6.32"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 120
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following TOML to YAML:\nprescriber = \"Melinda Black\"\ndate = \"2026-01-04\"\nrx_id = \"RX-8618237\"\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from TOML 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:\nprescriber: Melinda Black\ndate: '2026-01-04'\nrx_id: RX-8618237"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"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": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 234c0781-6e40-4e46-8b0d-ad1b39309eb0\ntimestamp: '2026-01-07T13:51:25.659911'\nlevel: WARNING\nservice: beyondService\nmessage: Section material entire top community.\nstack_trace:\n- at reason.py:320\n- at always.py:365\n- at red.py:27\ncontext:\n user_id: 6765bd92-f82e-426f-a383-fa0a088a0752\n request_id: 4ccfb0b5-8185-4d26-902a-0379b3534400"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 163
}
|
[
{
"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 CSV to XML:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nKDS432,CRS-9456,3,40,30,30,Kenneth Rogers,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"activity\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"foot\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"reason\"\"}, {\"\"w\",Fall 2020,Multi-channeled local complexity 101\r\nKXW117,CRS-6421,3,40,30,30,Shelley Scott,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"specific\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"well\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"wrong\"\"}, {\"\"we\",Fall 2020,Enterprise-wide 5thgeneration strategy 101\r\nNFV230,CRS-2609,3,40,30,30,Ashley Mccullough,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"such\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"bar\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"task\"\"}, {\"\"week\"\": 4\",Fall 2022,Cross-group non-volatile conglomeration 101\r\nSEY107,CRS-7967,3,40,30,30,Shane Smith,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"eight\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"material\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"site\"\"}, {\"\"we\",Fall 2023,Managed executive project 101\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from CSV 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<course_syllabus>\n<course_id>CRS-9456</course_id>\nKDS432\n<title>Multi-channeled local complexity 101</title>\n<instructor>Kenneth Rogers</instructor>\n<credits>3</credits>\n<term>Fall 2020</term>\n<schedule>\n<week>1</week>\n<topic>activity</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>foot</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>reason</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>rule</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>paper</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>current</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>scene</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>later</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>choice</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>box</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 314
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-160417</experiment_id>\n<title>Effect of agree on both</title>\n<methodology>\n<design>cohort</design>\n<sample_size>663</sample_size>\n<duration_days>354</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>13.92</baseline>\n<endpoint>49.07</endpoint>\n<p_value>0.4102</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>15.99</baseline>\n<endpoint>65.81</endpoint>\n<p_value>0.3043</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>46.51</baseline>\n<endpoint>82.23</endpoint>\n<p_value>0.4775</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"experiment_id\": \"EXP-160417\",\n \"title\": \"Effect of agree on both\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 663,\n \"duration_days\": 354\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 13.92,\n \"endpoint\": 49.07,\n \"p_value\": 0.4102\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 15.99,\n \"endpoint\": 65.81,\n \"p_value\": 0.3043\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 46.51,\n \"endpoint\": 82.23,\n \"p_value\": 0.4775\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 220
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"rx_id\": \"RX-1995080\",\n \"patient_mrn\": \"MRN-674224\",\n \"prescriber\": \"Emily Herrera\",\n \"date\": \"2026-01-05\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"BID\",\n \"quantity\": 60\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-1995080</rx_id>\n<patient_mrn>MRN-674224</patient_mrn>\n<prescriber>Emily Herrera</prescriber>\n<date>2026-01-05</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>10mg</dosage>\n<frequency>BID</frequency>\n<quantity>60</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 159
}
|
[
{
"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-1812594</result_id>\n<patient_mrn>MRN-755137</patient_mrn>\n<order_date>2026-01-06</order_date>\n<panel>CMP</panel>\n<results>\n<test>Glucose</test>\n<value>131.9</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>183.7</value>\n<unit>g/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>130.1</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>178.3</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n</lab_result>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 224
}
|
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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:\npaper_id = \"arXiv:2024.67669\"\ntitle = \"Triple-buffered dedicated knowledgebase\"\nabstract = \"Account fish possible democratic ok no. Accept short mention guy.\\nPlace finish religious mean end success. Travel into music they.\"\nkeywords = [ \"thank\", \"far\", \"fund\", \"get\", \"role\",]\ncitations = 60\nfunding_source = \"Diaz-Salinas\"\n[[authors]]\nname = \"Julie Mclaughlin\"\naffiliation = \"Andrews Group\"\nemail = \"brianna81@example.org\"\n\n[[authors]]\nname = \"Peggy Kramer\"\naffiliation = \"Beasley, Edwards and Webb\"\nemail = \"susan35@example.com\"\n\n[publication]\nvenue = \"Nature\"\nyear = 2023\ndoi = \"10.1349/JgWc\""
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 223
}
|
[
{
"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 \"review_id\": \"REV-2691236\",\n \"product_id\": \"PROD-245093\",\n \"user_id\": \"98b0ec97-f0e6-4eda-907b-c1488d5de2f5\",\n \"rating\": 1,\n \"title\": \"Now new sell exist just.\",\n \"content\": \"Issue suddenly such maybe. Military they second staff end agreement.\\nClose that speech alone know wish matter. Finally adult statement method.\",\n \"date\": \"2026-01-02\",\n \"verified_purchase\": false,\n \"helpful_votes\": 34\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-2691236</review_id>\n<product_id>PROD-245093</product_id>\n<user_id>98b0ec97-f0e6-4eda-907b-c1488d5de2f5</user_id>\n<rating>1</rating>\n<title>Now new sell exist just.</title>\n<content>Issue suddenly such maybe. Military they second staff end agreement.\nClose that speech alone know wish matter. Finally adult statement method.</content>\n<date>2026-01-02</date>\n<verified_purchase>False</verified_purchase>\n<helpful_votes>34</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 211
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Convert the following JSON to CSV:\n{\n \"rx_id\": \"RX-7309915\",\n \"patient_mrn\": \"MRN-389849\",\n \"prescriber\": \"Briana Dickerson\",\n \"date\": \"2026-01-03\",\n \"medications\": [\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to 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. Transform values to match the target format specifications.\n\nOutput:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-03,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 30}]\",MRN-389849,Briana Dickerson,RX-7309915\r\n2026-01-04,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 90}, {\"\"name\"\": \"\"Atorvast\",MRN-282226,Brenda Roberson,RX-8074644\r\n2026-01-03,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 90}]\",MRN-937202,Jacob Taylor,RX-8384566\r\n2026-01-03,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Atorvastatin\",MRN-446981,Jessica Smith,RX-2483272"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 246
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-239354\",\n \"name\": \"User-centric tertiary contingency\",\n \"category\": \"electronics\",\n \"price\": 998.51,\n \"currency\": \"USD\",\n \"stock\": 842,\n \"is_available\": true,\n \"rating\": 2.36,\n \"reviews\": 630,\n \"specs\": {\n \"weight_kg\": 0.61,\n \"dimensions\": \"88x23x10cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 152
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate api specification data in XML format."
},
{
"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>Re-engineered mobile superstructure API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</benefit>\n<get>\n<summary>Chair media space recognize doctor would second me</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>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//benefit>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 251
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<financial_report>\n<net_income>16280737</net_income>\n<revenue>93235840</revenue>\n<metrics>\n<profit_margin>9.67</profit_margin>\n<roe>5.79</roe>\n</metrics>\n<expenses>6835352</expenses>\n</financial_report>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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:\nnet_income: 16280737\nrevenue: 93235840\nmetrics:\n profit_margin: 9.67\n roe: 5.79\nexpenses: 6835352"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 105
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-574681</experiment_id>\n<title>Effect of anyone on society</title>\n<methodology>\n<design>cohort</design>\n<sample_size>560</sample_size>\n<duration_days>320</duration_days>\n</methodology>\n<results>\n<metric>efficacy</metric>\n<baseline>50.77</baseline>\n<endpoint>70.83</endpoint>\n<p_value>0.3046</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>96.52</baseline>\n<endpoint>82.25</endpoint>\n<p_value>0.0326</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>43.38</baseline>\n<endpoint>72.88</endpoint>\n<p_value>0.2787</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>17.71</baseline>\n<endpoint>95.37</endpoint>\n<p_value>0.4542</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"experiment_id\": \"EXP-574681\",\n \"title\": \"Effect of anyone on society\",\n \"methodology\": {\n \"design\": \"cohort\",\n \"sample_size\": 560,\n \"duration_days\": 320\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 50.77,\n \"endpoint\": 70.83,\n \"p_value\": 0.3046\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 96.52,\n \"endpoint\": 82.25,\n \"p_value\": 0.0326\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 43.38,\n \"endpoint\": 72.88,\n \"p_value\": 0.2787\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 17.71,\n \"endpoint\": 95.37,\n \"p_value\": 0.4542\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 250
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output customer review as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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,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,Team hold course throw center open enjoy old. Huge candidate still act decade civil. Safe middle ind,,2026-01-03,98,,,,PROD-754494,5,REV-4235678,,,,,Help program law water necessary return clearly.,29638f7d-f697-4ae7-8fde-a1a70bcd6476,False\r\nelectronics,,USD,,,True,Horizontal global infrastructure,445.65,PROD-347551,2.38,,773,49x46x92cm,19.96,601,,,\r\nelectronics,,USD,,,True,Stand-alone 3rdgeneration success,681.89,PROD-911721,2.97,,562,24x48x96cm,22.35,714,,,"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 237
}
|
[
{
"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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Re-engineered mobile superstructure API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/benefit\": {\n \"get\": {\n \"summary\": \"Chair media space recognize doctor would second me\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Re-engineered mobile superstructure API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</benefit>\n<get>\n<summary>Chair media space recognize doctor would second me</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>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//benefit>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 253
}
|
[
{
"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 CSV to YAML:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\nBody exactly last operation trouble. Financial whole check management chance eat us. Likely wrong ex,\"[{\"\"name\"\": \"\"David Cohen\"\", \"\"affiliation\"\": \"\"Lopez and Sons\"\", \"\"email\"\": \"\"mark98@example.com\"\"}, {\"\"name\"\": \"\"\",174,None,\"[\"\"rather\"\", \"\"hair\"\", \"\"attorney\"\", \"\"chance\"\", \"\"bring\"\"]\",arXiv:2024.66116,10.7468/EeJM,Cell,2020,Quality-focused grid-enabled service-desk\r\n\"Especially room explain kid would listen subject.\nWrite man him six enjoy season rest. Few less minu\",\"[{\"\"name\"\": \"\"Ashley Howard\"\", \"\"affiliation\"\": \"\"Jackson-Moore\"\", \"\"email\"\": \"\"turnercharles@example.com\"\"}, {\"\"\",44,\"Mercer, Ruiz and Wright\",\"[\"\"measure\"\", \"\"reflect\"\", \"\"discover\"\", \"\"future\"\"]\",arXiv:2024.31155,10.1812/jZeP,Science,2021,Sharable real-time system engine\r\nReflect end note movement civil successful surface once. Experience life teacher between long traini,\"[{\"\"name\"\": \"\"Alejandro Young\"\", \"\"affiliation\"\": \"\"Castillo-Cox\"\", \"\"email\"\": \"\"howardjessica@example.com\"\"}, {\",248,\"Rivera, James and Jones\",\"[\"\"spend\"\", \"\"them\"\", \"\"late\"\", \"\"risk\"\"]\",arXiv:2022.69649,10.2689/ADsC,Nature,2020,Realigned 6thgeneration archive\r\nNext avoid lot while development feeling result. Friend boy full sea which can performance.,\"[{\"\"name\"\": \"\"Laura Aguilar\"\", \"\"affiliation\"\": \"\"Wade PLC\"\", \"\"email\"\": \"\"urobinson@example.org\"\"}, {\"\"name\"\": \"\"J\",171,Bell LLC,\"[\"\"there\"\", \"\"ability\"\", \"\"theory\"\", \"\"list\"\", \"\"maintain\"\"]\",arXiv:2020.56309,10.9367/bePU,Science,2022,Cross-platform zero administration encoding\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\npaper_id: arXiv:2024.66116\ntitle: Quality-focused grid-enabled service-desk\nauthors:\n- name: David Cohen\n affiliation: Lopez and Sons\n email: mark98@example.com\n- name: Ashley Spencer\n affiliation: Hood Ltd\n email: pbailey@example.org\n- name: Robin Lynch\n affiliation: Camacho, Nelson and Perez\n email: samantha44@example.net\nabstract: Body exactly last operation trouble. Financial whole check management chance\n eat us. Likely wrong explain by would born only.\nkeywords:\n- rather\n- hair\n- attorney\n- chance\n- bring\npublication:\n venue: Cell\n year: 2020\n doi: 10.7468/EeJM\ncitations: 174\nfunding_source: null"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 233
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate customer review data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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 \"review_id\": \"REV-4235678\",\n \"product_id\": \"PROD-754494\",\n \"user_id\": \"29638f7d-f697-4ae7-8fde-a1a70bcd6476\",\n \"rating\": 5,\n \"title\": \"Help program law water necessary return clearly.\",\n \"content\": \"Team hold course throw center open enjoy old. Huge candidate still act decade civil. Safe middle indeed.\",\n \"date\": \"2026-01-03\",\n \"verified_purchase\": false,\n \"helpful_votes\": 98\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 175
}
|
[
{
"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 YAML to XML:\ndate: '2026-01-06'\npatient_mrn: MRN-259808\nrx_id: RX-8539167\nprescriber: Joseph Griffin\nmedications:\n- name: Atorvastatin\n dosage: 10mg\n frequency: daily\n quantity: 90\n- name: Lisinopril\n dosage: 10mg\n frequency: TID\n quantity: 30\n- name: Metformin\n dosage: 5mg\n frequency: BID\n quantity: 30\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from YAML 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<prescription>\n<date>2026-01-06</date>\n<patient_mrn>MRN-259808</patient_mrn>\n<rx_id>RX-8539167</rx_id>\n<prescriber>Joseph Griffin</prescriber>\n<medications>\n<name>Atorvastatin</name>\n<dosage>10mg</dosage>\n<frequency>daily</frequency>\n<quantity>90</quantity>\n</medications>\n<medications>\n<name>Lisinopril</name>\n<dosage>10mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Metformin</name>\n<dosage>5mg</dosage>\n<frequency>BID</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 223
}
|
[
{
"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<clinical_note>\n<note_id>CN-3409162</note_id>\n<patient>\n<mrn>MRN-721241</mrn>\n<age>35</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-05</encounter_date>\n<chief_complaint>fever</chief_complaint>\n<vitals>\n<bp>173/107</bp>\n<hr>61</hr>\n<temp_f>99.6</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>J46</icd10>\n</assessment>\n</clinical_note>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"note_id\": \"CN-3409162\",\n \"patient\": {\n \"mrn\": \"MRN-721241\",\n \"age\": 35,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-05\",\n \"chief_complaint\": \"fever\",\n \"vitals\": {\n \"bp\": \"173/107\",\n \"hr\": 61,\n \"temp_f\": 99.6\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J46\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 160
}
|
[
{
"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 YAML to JSON:\narticle_id: ART-3682408\nheadline: Decentralized stable neural-net\nauthor: Thomas Acevedo\npublished: '2026-01-01T11:30:40.673887'\nsection: Business\ncontent: 'Cold trial recognize improve nice between these. Happy herself suggest impact\n tell easy.\n\n Start movie up social real effort. Onto federal prepare class direction rest.\n\n News party school five bit. Trouble box year how.\n\n Pressure respond nature. Prepare ball put happen.'\ntags:\n- movie\n- it\n- chance\nviews: 12438\nshares: 1329\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article 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 \"article_id\": \"ART-3682408\",\n \"headline\": \"Decentralized stable neural-net\",\n \"author\": \"Thomas Acevedo\",\n \"published\": \"2026-01-01T11:30:40.673887\",\n \"section\": \"Business\",\n \"content\": \"Cold trial recognize improve nice between these. Happy herself suggest impact tell easy.\\nStart movie up social real effort. Onto federal prepare class direction rest.\\nNews party school five bit. Trouble box year how.\\nPressure respond nature. Prepare ball put happen.\",\n \"tags\": [\n \"movie\",\n \"it\",\n \"chance\"\n ],\n \"views\": 12438,\n \"shares\": 1329\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 217
}
|
[
{
"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 sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nperiod: June 2022\ntotal_revenue: 7287772\nunits_sold: 8566\nchannels:\n- name: retail\n revenue: 931216\n growth: 10.96\n- name: wholesale\n revenue: 1224016\n growth: 31.92\ntop_products:\n- sku: SKU-1474\n sales: 19268\n- sku: SKU-3289\n sales: 31397\n- sku: SKU-4950\n sales: 322920"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 147
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"note_id\": \"CN-3766387\",\n \"patient\": {\n \"mrn\": \"MRN-378219\",\n \"age\": 48,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-04\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"145/101\",\n \"hr\": 106,\n \"temp_f\": 101.7\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J94\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-3766387</note_id>\n<patient>\n<mrn>MRN-378219</mrn>\n<age>48</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>145/101</bp>\n<hr>106</hr>\n<temp_f>101.7</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>J94</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 181
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output customer review as CSV."
},
{
"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,North describe old attention usually third. Important wish security ago somebody remain everyone mod,,2026-01-04,34,,,,PROD-452864,3,REV-9982202,,,,,Example center fill free.,015289de-7f3e-45e2-b1d0-7fe22aff92a9,False\r\nbooks,,USD,,,True,Open-source uniform capability,301.27,PROD-318199,4.66,,24,81x14x96cm,40.6,54,,,\r\nbooks,,USD,,,True,Reactive 4thgeneration contingency,189.15,PROD-546709,3.83,,865,33x54x28cm,22.27,209,,,\r\nbooks,,USD,,,True,Cross-platform grid-enabled leverage,653.55,PROD-287286,3.19,,34,64x17x56cm,47.51,891,,,"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 255
}
|
[
{
"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:2024.66116\",\n \"title\": \"Quality-focused grid-enabled service-desk\",\n \"authors\": [\n {\n \"name\": \"David Cohen\",\n \"affiliation\": \"Lopez and Sons\",\n \"email\": \"mark98@example.com\"\n },\n {\n \"name\": \"Ashley Spencer\",\n \"affiliation\": \"Hood Ltd\",\n \"email\": \"pbailey@example.org\"\n },\n {\n \"name\": \"Robin Lynch\",\n \"affiliation\": \"Camacho, Nelson and Perez\",\n \"email\": \"samantha44@example.net\"\n }\n ],\n \"abstract\": \"Body exactly last operation trouble. Financial whole check management chance eat us. Likely wrong explain by would born only.\",\n \"keywords\": [\n \"rather\",\n \"hair\",\n \"attorney\",\n \"chance\",\n \"bring\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2020,\n \"doi\": \"10.7468/EeJM\"\n },\n \"citations\": 174,\n \"funding_source\": null\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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<research_paper>\n<paper_id>arXiv:2024.66116</paper_id>\n<title>Quality-focused grid-enabled service-desk</title>\n<authors>\n<name>David Cohen</name>\n<affiliation>Lopez and Sons</affiliation>\n<email>mark98@example.com</email>\n</authors>\n<authors>\n<name>Ashley Spencer</name>\n<affiliation>Hood Ltd</affiliation>\n<email>pbailey@example.org</email>\n</authors>\n<authors>\n<name>Robin Lynch</name>\n<affiliation>Camacho, Nelson and Perez</affiliation>\n<email>samantha44@example.net</email>\n</authors>\n<abstract>Body exactly last operation trouble. Financial whole check management chance eat us. Likely wrong explain by would born only.</abstract>\n<keywords>rather</keywords>\n<keywords>hair</keywords>\n<keywords>attorney</keywords>\n<keywords>chance</keywords>\n<keywords>bring</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2020</year>\n<doi>10.7468/EeJM</doi>\n</publication>\n<citations>174</citations>\n<funding_source />\n</research_paper>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 321
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output course syllabus as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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 \"instructor\": \"Tamara Stark\",\n \"term\": \"Spring 2022\",\n \"code\": \"VMA483\",\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 117
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. , then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output sales analytics as TOML."
},
{
"role": "assistant",
"content": "period = \"April 2020\"\ntotal_revenue = 1914989\nunits_sold = 47758\n[[channels]]\nname = \"wholesale\"\nrevenue = 3617590\ngrowth = 20.48\n\n[[channels]]\nname = \"online\"\nrevenue = 654207\ngrowth = 24.4\n\n[[top_products]]\nsku = \"SKU-4328\"\nsales = 466200\n\n[[top_products]]\nsku = \"SKU-2589\"\nsales = 244105\n\n[[top_products]]\nsku = \"SKU-7725\"\nsales = 25778"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 159
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn_id>TXN-79156891</txn_id>\n<customer_id>5450ecc9-30b8-498f-a527-04ec3de16dd8</customer_id>\n<timestamp>2026-01-07T13:51:26.258900</timestamp>\n<items>\n<sku>SKU-81880</sku>\n<qty>4</qty>\n<price>401.7</price>\n</items>\n<items>\n<sku>SKU-99718</sku>\n<qty>5</qty>\n<price>334.37</price>\n</items>\n<items>\n<sku>SKU-65882</sku>\n<qty>3</qty>\n<price>292.8</price>\n</items>\n<items>\n<sku>SKU-88201</sku>\n<qty>2</qty>\n<price>114.91</price>\n</items>\n<subtotal>258.62</subtotal>\n<tax>22.79</tax>\n<total>1713.37</total>\n<payment_method>paypal</payment_method>\n</transaction_record>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record 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:\ntxn_id: TXN-79156891\ncustomer_id: 5450ecc9-30b8-498f-a527-04ec3de16dd8\ntimestamp: '2026-01-07T13:51:26.258900'\nitems:\n- sku: SKU-81880\n qty: 4\n price: 401.7\n- sku: SKU-99718\n qty: 5\n price: 334.37\n- sku: SKU-65882\n qty: 3\n price: 292.8\n- sku: SKU-88201\n qty: 2\n price: 114.91\nsubtotal: 258.62\ntax: 22.79\ntotal: 1713.37\npayment_method: paypal"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 167
}
|
[
{
"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 = \"92d36993-19b1-4c19-9b64-8b4669c6636f\"\ntimestamp = \"2026-01-07T13:51:27.222487\"\nlevel = \"WARNING\"\nservice = \"voiceService\"\nmessage = \"Analysis beautiful attack blue eye.\"\nstack_trace = [ \"at well.py:163\", \"at will.py:421\", \"at run.py:384\", \"at TV.py:103\",]\n\n[context]\nuser_id = \"c92bcb8f-c109-47f8-aa13-b43737a1fc38\"\nrequest_id = \"f4cb6737-30c9-41ef-814b-34c3ec971deb\""
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 167
}
|
[
{
"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 error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: a016c8d2-6aba-435a-ab46-60ac8aacf0a5\ntimestamp: '2026-01-07T13:51:26.006823'\nlevel: CRITICAL\nservice: currentService\nmessage: Well nation stay number now but.\nstack_trace:\n- at daughter.py:364\n- at same.py:66\ncontext:\n user_id: 432ef3ee-7f2b-4bc8-a8a7-159d64a89fd5\n request_id: 4ed63374-fc09-4101-b987-4a8ee575fee3"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 158
}
|
[
{
"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 prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription 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:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-05,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 90}]\",MRN-440463,Lisa Mathews,RX-6036951\r\n2026-01-06,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 90}]\",MRN-374219,Kyle Arnold,RX-9467282\r\n2026-01-03,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 90}]\",MRN-404153,Tyler Day,RX-6466107\r\n2026-01-02,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 60}]\",MRN-983646,Joshua Jennings,RX-9128747"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 230
}
|
[
{
"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 course syllabus."
},
{
"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\n,CRS-8305,4,,,,Rachel Moreno DVM,,Spring 2023,Open-architected even-keeled support 101\r\nCNK133,CRS-5922,3,40,30,30,Tammy Scott,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"team\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"much\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"executive\"\"}, {\"\"we\",Fall 2022,Diverse homogeneous access 101\r\nTDW280,CRS-9943,4,40,30,30,Christine Hamilton,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"matter\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"black\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"your\"\"}, {\"\"week\",Fall 2021,Decentralized interactive project 101"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 230
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-6224145</note_id>\n<patient>\n<mrn>MRN-560569</mrn>\n<age>88</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>119/73</bp>\n<hr>63</hr>\n<temp_f>100.0</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>I32</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 180
}
|
[
{
"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 \"experiment_id\": \"EXP-330074\",\n \"title\": \"Effect of politics on stop\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 328,\n \"duration_days\": 247\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 34.54,\n \"endpoint\": 53.32,\n \"p_value\": 0.0487\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 10.4,\n \"endpoint\": 13.84,\n \"p_value\": 0.1164\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 78.27,\n \"endpoint\": 47.78,\n \"p_value\": 0.0781\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result 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:\nexperiment_id: EXP-330074\ntitle: Effect of politics on stop\nmethodology:\n design: RCT\n sample_size: 328\n duration_days: 247\nresults:\n- metric: efficacy\n baseline: 34.54\n endpoint: 53.32\n p_value: 0.0487\n- metric: safety\n baseline: 10.4\n endpoint: 13.84\n p_value: 0.1164\n- metric: efficacy\n baseline: 78.27\n endpoint: 47.78\n p_value: 0.0781\nconclusion: non-significant"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 174
}
|
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ntxn_id = \"TXN-85338602\"\ncustomer_id = \"ea7970e3-49c7-4d3a-bbe0-6c539dc6c3d3\"\ntimestamp = \"2026-01-07T13:51:25.620781\"\nsubtotal = 468.67\ntax = 148.91\ntotal = 792.01\npayment_method = \"apple_pay\"\n[[items]]\nsku = \"SKU-22630\"\nqty = 3\nprice = 89.97"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 136
}
|
[
{
"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 TOML to XML:\nexperiment_id = \"EXP-139463\"\ntitle = \"Effect of quite on arm\"\nconclusion = \"non-significant\"\n[[results]]\nmetric = \"safety\"\nbaseline = 91.61\nendpoint = 76.9\np_value = 0.4003\n\n[[results]]\nmetric = \"safety\"\nbaseline = 58.96\nendpoint = 23.83\np_value = 0.3437\n\n[[results]]\nmetric = \"safety\"\nbaseline = 23.31\nendpoint = 88.63\np_value = 0.3018\n\n[methodology]\ndesign = \"RCT\"\nsample_size = 371\nduration_days = 284\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from TOML 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<experiment_result>\n<experiment_id>EXP-139463</experiment_id>\n<title>Effect of quite on arm</title>\n<methodology>\n<design>RCT</design>\n<sample_size>371</sample_size>\n<duration_days>284</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>91.61</baseline>\n<endpoint>76.9</endpoint>\n<p_value>0.4003</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>58.96</baseline>\n<endpoint>23.83</endpoint>\n<p_value>0.3437</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>23.31</baseline>\n<endpoint>88.63</endpoint>\n<p_value>0.3018</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 251
}
|
[
{
"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: 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:\neps: 6.0\ncompany: Richardson-Gonzalez\nquarter: Q3 2020\nnet_income: 13953656"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 98
}
|
[
{
"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<course_syllabus>\n<course_id>CRS-2063</course_id>\n<code>FAH301</code>\n<title>Ameliorated zero administration productivity 101</title>\n<instructor>Aaron Bailey</instructor>\n<credits>4</credits>\n<term>Fall 2023</term>\n<schedule>\n<week>1</week>\n<topic>health</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>buy</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>conference</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>late</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>fear</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>ability</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>control</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>choose</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>measure</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>social</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 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 \"course_id\": \"CRS-2063\",\n \"code\": \"FAH301\",\n \"title\": \"Ameliorated zero administration productivity 101\",\n \"instructor\": \"Aaron Bailey\",\n \"credits\": 4,\n \"term\": \"Fall 2023\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"health\"\n },\n {\n \"week\": 2,\n \"topic\": \"buy\"\n },\n {\n \"week\": 3,\n \"topic\": \"conference\"\n },\n {\n \"week\": 4,\n \"topic\": \"late\"\n },\n {\n \"week\": 5,\n \"topic\": \"fear\"\n },\n {\n \"week\": 6,\n \"topic\": \"ability\"\n },\n {\n \"week\": 7,\n \"topic\": \"control\"\n },\n {\n \"week\": 8,\n \"topic\": \"choose\"\n },\n {\n \"week\": 9,\n \"topic\": \"measure\"\n },\n {\n \"week\": 10,\n \"topic\": \"social\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 284
}
|
[
{
"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 \"product_id\": \"PROD-428311\",\n \"name\": \"Object-based value-added workforce\",\n \"category\": \"books\",\n \"price\": 802.3,\n \"currency\": \"USD\",\n \"stock\": 719,\n \"is_available\": true,\n \"rating\": 1.5,\n \"reviews\": 81,\n \"specs\": {\n \"weight_kg\": 27.85,\n \"dimensions\": \"99x87x32cm\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing 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<product_listing>\n<product_id>PROD-428311</product_id>\n<name>Object-based value-added workforce</name>\n<category>books</category>\n<price>802.3</price>\n<currency>USD</currency>\n<stock>719</stock>\n<is_available>True</is_available>\n<rating>1.5</rating>\n<reviews>81</reviews>\n<specs>\n<weight_kg>27.85</weight_kg>\n<dimensions>99x87x32cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 181
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nitems:\n- sku: SKU-71565\n qty: 1\n price: 387.38\n- sku: SKU-23891\n qty: 1\n price: 432.74\n- sku: SKU-77840\n qty: 1\n price: 463.12\n- sku: SKU-27496\n qty: 3\n price: 295.3\ntax: 39.55\ntotal: 1865.58\ncustomer_id: bf96f80b-072c-4f04-82b0-c235c01681a8"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 142
}
|
[
{
"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 error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 424897c8-d97d-4bfb-9c1a-7b6e63fd6096\ntimestamp: '2026-01-07T13:51:27.529237'\nlevel: ERROR\nservice: heartService\nmessage: How these anyone stop indeed.\nstack_trace:\n- at manage.py:289\n- at thing.py:107\n- at guy.py:172\n- at seat.py:479\ncontext:\n user_id: 082cc3eb-3997-4d99-990c-f696ca4ee534\n request_id: 0f3326d0-3afd-48c1-9c4d-32cc8b0c5920"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 164
}
|
[
{
"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: 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\": \"Tucker and Sons\",\n \"ticker\": \"BPQE\",\n \"quarter\": \"Q4 2024\",\n \"revenue\": 70279854,\n \"expenses\": 61737533,\n \"net_income\": 12235621,\n \"eps\": 3.52,\n \"metrics\": {\n \"profit_margin\": 24.27,\n \"roe\": 16.15\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 135
}
|
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id: EXP-690622\ntitle: Effect of drug on effect\nmethodology:\n design: RCT\n sample_size: 718\n duration_days: 247\nresults:\n- metric: efficacy\n baseline: 65.65\n endpoint: 47.19\n p_value: 0.4009\n- metric: efficacy\n baseline: 18.88\n endpoint: 49.79\n p_value: 0.0184\n- metric: efficacy\n baseline: 32.37\n endpoint: 97.44\n p_value: 0.3919\nconclusion: non-significant"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 174
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\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\"\": \"\"I12\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K62\"\"}]\",chest pain,2026-01-02,CN-4315709,89,M,MRN-534874,165/61,112,99.4\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J39\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K19\"\"}]\",headache,2026-01-02,CN-9175166,77,F,MRN-849686,118/64,86,101.3\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K77\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J61\"\"}]\",fever,2026-01-03,CN-4266501,18,M,MRN-721513,124/95,119,101.3\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nnote_id: CN-4315709\npatient:\n mrn: MRN-534874\n age: 89\n gender: M\nencounter_date: '2026-01-02'\nchief_complaint: chest pain\nvitals:\n bp: 165/61\n hr: 112\n temp_f: 99.4\nassessment:\n- problem: diabetes\n icd10: I12\n- problem: diabetes\n icd10: K62"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 141
}
|
[
{
"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 product listing."
},
{
"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-891981\"\nname = \"Focused background info-mediaries\"\ncategory = \"books\"\nprice = 16.4\ncurrency = \"USD\"\nstock = 192\nis_available = true\nrating = 3.23\nreviews = 117\n\n[specs]\nweight_kg = 31.51\ndimensions = \"65x39x62cm\""
}
] |
{
"format": "toml",
"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": "Create a YAML representation of student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\nassessment_id: ASMT-530397\nstudent_id: STU-509684\ncourse_id: CRS-8191\ntype: quiz\ndate: '2026-01-01'\nscores:\n- question: 1\n points_earned: 3\n points_possible: 10\n- question: 2\n points_earned: 5\n points_possible: 10\n- question: 3\n points_earned: 4\n points_possible: 10\n- question: 4\n points_earned: 6\n points_possible: 10\n- question: 5\n points_earned: 0\n points_possible: 10\n- question: 6\n points_earned: 9\n points_possible: 10\n- question: 7\n points_earned: 3\n points_possible: 10\n- question: 8\n points_earned: 6\n points_possible: 10\n- question: 9\n points_earned: 5\n points_possible: 10\n- question: 10\n points_earned: 10\n points_possible: 10\n- question: 11\n points_earned: 7\n points_possible: 10\n- question: 12\n points_earned: 9\n points_possible: 10\n- question: 13\n points_earned: 2\n points_possible: 10\n- question: 14\n points_earned: 7\n points_possible: 10\ntotal_score: 91\npercentage: 61.03\ngrade: A"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 310
}
|
[
{
"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 = \"Streamlined logistical help-desk API\"\nversion = \"1.0.0\"\n\n[paths.\"/grow\".get]\nsummary = \"Will entire deep source history.\"\n[[paths.\"/grow\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/grow\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/grow\".get.parameters]]\nname = \"param2\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/grow\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/grow\".get.responses.400]\ndescription = \"Bad Request\""
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 204
}
|
[
{
"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<financial_report>\n<company>Nichols, Ferguson and Butler</company>\n<ticker>NDVN</ticker>\n<quarter>Q1 2022</quarter>\n<revenue>39470251</revenue>\n<expenses>26562838</expenses>\n<net_income>16784469</net_income>\n<eps>3.2</eps>\n<metrics>\n<profit_margin>27.93</profit_margin>\n<roe>5.96</roe>\n</metrics>\n</financial_report>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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 \"company\": \"Nichols, Ferguson and Butler\",\n \"ticker\": \"NDVN\",\n \"quarter\": \"Q1 2022\",\n \"revenue\": 39470251,\n \"expenses\": 26562838,\n \"net_income\": 16784469,\n \"eps\": 3.2,\n \"metrics\": {\n \"profit_margin\": 27.93,\n \"roe\": 5.96\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 140
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Convert the following XML to CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course_id>CRS-9141</course_id>\n<code>ESH384</code>\n<title>Inverse real-time hardware 101</title>\n<instructor>Matthew Boyd</instructor>\n<credits>4</credits>\n<term>Fall 2022</term>\n<schedule>\n<week>1</week>\n<topic>western</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>since</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>later</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>next</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>tree</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>until</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>everything</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>until</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>how</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>test</topic>\n</schedule>\n<schedule>\n<week>11</week>\n<topic>half</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 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. Transform values to match the target format specifications.\n\nOutput:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nESH384,CRS-9141,4,40,30,30,Matthew Boyd,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"western\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"since\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"later\"\"}, {\"\"we\",Fall 2022,Inverse real-time hardware 101\r\nJKU244,CRS-6370,3,40,30,30,Teresa Davis,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"nearly\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"base\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"already\"\"}, {\"\"we\",Fall 2021,Reactive 4thgeneration parallelism 101\r\nHEF399,CRS-4457,4,40,30,30,Alexander Dominguez,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"may\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"beat\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"find\"\"}, {\"\"week\"\": 4\",Spring 2023,User-friendly 24hour customer loyalty 101\r\nZLN329,CRS-9809,3,40,30,30,Eddie Keller DDS,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"put\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"travel\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"he\"\"}, {\"\"week\"\": 4\",Fall 2020,Enterprise-wide interactive orchestration 101"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 320
}
|
[
{
"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<financial_report>\n<revenue>81140617</revenue>\n<metrics>\n<profit_margin>25.46</profit_margin>\n<roe>20.6</roe>\n</metrics>\n<quarter>Q1 2021</quarter>\n</financial_report>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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 \"revenue\": 81140617,\n \"metrics\": {\n \"profit_margin\": 25.46,\n \"roe\": 20.6\n },\n \"quarter\": \"Q1 2021\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 108
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output error log as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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<error_log>\n<error_id>2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f</error_id>\n<timestamp>2026-01-07T13:51:25.611338</timestamp>\n<level>ERROR</level>\n<service>typeService</service>\n<message>Suggest involve part skill write left participant.</message>\n<stack_trace>at risk.py:441</stack_trace>\n<stack_trace>at strategy.py:390</stack_trace>\n<stack_trace>at performance.py:267</stack_trace>\n<stack_trace>at kind.py:265</stack_trace>\n<context>\n<user_id>3651fff2-dc6a-4fe5-a964-ed26913f3e4b</user_id>\n<request_id>f4fc48f0-6374-4e80-b666-89c2abac0904</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 228
}
|
[
{
"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 customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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,date,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title,user_id\r\n,,,It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment te,2026-01-04,,,,,,,,d6e6e646-61a4-4af9-a9a1-d03d234244eb\r\nSport eight century too everyone. Direction very relate order toward.,\"[{\"\"name\"\": \"\"Joseph Orozco\"\", \"\"affiliation\"\": \"\"Flores, Clark and Krause\"\", \"\"email\"\": \"\"crawfordheidi@exampl\",321,,,None,\"[\"\"history\"\", \"\"information\"\", \"\"discuss\"\", \"\"fine\"\"]\",arXiv:2021.57597,10.7112/HFuP,Nature,2020,Inverse non-volatile protocol,\r\nStart old reflect agreement heavy water. Action should travel career. Difficult arrive act summer pr,\"[{\"\"name\"\": \"\"Lisa Richmond\"\", \"\"affiliation\"\": \"\"Smith-Taylor\"\", \"\"email\"\": \"\"brownjonathan@example.net\"\"}, {\"\"n\",33,,,None,\"[\"\"training\"\", \"\"stage\"\", \"\"support\"\"]\",arXiv:2020.79870,10.7699/PryY,Nature,2024,Focused attitude-oriented website,"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 320
}
|
[
{
"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 \"post_id\": \"POST-25055870\",\n \"platform\": \"twitter\",\n \"user_id\": \"28837af0-4898-41b2-8a38-faf0e2d7f431\",\n \"username\": \"khahn\",\n \"content\": \"Serve student science today general. Tell risk ball quickly technology.\\nDrive because generation support gun message majority. Though do old.\",\n \"timestamp\": \"2026-01-07T13:51:27.403909\",\n \"hashtags\": [\n \"#conference\",\n \"#body\"\n ],\n \"engagement\": {\n \"likes\": 9394,\n \"shares\": 444,\n \"comments\": 203\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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<social_media_post>\n<post_id>POST-25055870</post_id>\n<platform>twitter</platform>\n<user_id>28837af0-4898-41b2-8a38-faf0e2d7f431</user_id>\n<username>khahn</username>\n<content>Serve student science today general. Tell risk ball quickly technology.\nDrive because generation support gun message majority. Though do old.</content>\n<timestamp>2026-01-07T13:51:27.403909</timestamp>\n<hashtags>#conference</hashtags>\n<hashtags>#body</hashtags>\n<engagement>\n<likes>9394</likes>\n<shares>444</shares>\n<comments>203</comments>\n</engagement>\n</social_media_post>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 226
}
|
[
{
"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 customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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,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,\"Chair painting shake city kind good though. Find reality water support key.\nFly party couple product\",,2026-01-03,78,,,,PROD-375265,1,REV-7250124,,,,,Very responsibility coach economy sea public you.,48302d32-0445-4405-afc6-604ef6300782,True\r\nelectronics,,USD,,,True,Universal neutral function,429.38,PROD-319216,4.22,,148,65x94x100cm,21.4,416,,,\r\nclothing,,USD,,,True,Proactive maximized emulation,617.13,PROD-960862,4.88,,767,77x65x72cm,31.38,920,,,\r\nelectronics,,USD,,,True,Secured tertiary middleware,488.02,PROD-145422,4.57,,492,33x70x73cm,16.37,747,,,"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 261
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output clinical note as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-8293808\",\n \"patient\": {\n \"mrn\": \"MRN-980604\",\n \"age\": 24,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-05\",\n \"chief_complaint\": \"fever\",\n \"vitals\": {\n \"bp\": \"150/98\",\n \"hr\": 93,\n \"temp_f\": 102.4\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J39\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 159
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output social media post as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-90196326\"\nplatform = \"facebook\"\nuser_id = \"146c178d-e548-4357-8cd4-e8464cea2f9b\"\nusername = \"kevincunningham\"\ncontent = \"Three would identify method across operation opportunity.\\nWhat realize number. Country perform simple team player. Improve order east mother news magazine trade.\\nCentral thus simple thousand morning.\"\ntimestamp = \"2026-01-07T13:51:26.698310\"\nhashtags = [ \"#pay\", \"#keep\",]\n\n[engagement]\nlikes = 458\nshares = 383\ncomments = 63"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 191
}
|
[
{
"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>Secured well-modulated policy API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</article>\n<get>\n<summary>During certainly full.</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>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//article>\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 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<sales_analytics>\n<total_revenue>6798538</total_revenue>\n<channels>\n<name>online</name>\n<revenue>2139770</revenue>\n<growth>-9.99</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>1809716</revenue>\n<growth>7.01</growth>\n</channels>\n<top_products>\n<sku>SKU-3049</sku>\n<sales>22854</sales>\n</top_products>\n<top_products>\n<sku>SKU-5505</sku>\n<sales>203281</sales>\n</top_products>\n<top_products>\n<sku>SKU-9853</sku>\n<sales>260538</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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 \"total_revenue\": 6798538,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 2139770,\n \"growth\": -9.99\n },\n {\n \"name\": \"retail\",\n \"revenue\": 1809716,\n \"growth\": 7.01\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-3049\",\n \"sales\": 22854\n },\n {\n \"sku\": \"SKU-5505\",\n \"sales\": 203281\n },\n {\n \"sku\": \"SKU-9853\",\n \"sales\": 260538\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 185
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output contract as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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:\ncontract_id = \"CTR-457828\"\neffective_date = \"2026-01-01\"\nterm_months = 32"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 92
}
|
[
{
"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 course syllabus."
},
{
"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\nNHA456,CRS-2281,3,40,30,30,Natalie Middleton,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"its\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"attorney\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"decision\"\"}, {\"\"\",Spring 2024,Profit-focused mission-critical hardware 101\r\nNMW222,CRS-2495,3,40,30,30,Kylie Davis,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"trial\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"night\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"financial\"\"}, {\"\"\",Spring 2020,Ergonomic intangible product 101\r\nUMT270,CRS-2420,3,40,30,30,Katrina Jensen,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"national\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"through\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"seat\"\"}, {\"\"\",Spring 2020,Programmable national migration 101\r\nOFO453,CRS-6448,4,40,30,30,Jeffrey Nunez MD,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"above\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"nation\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"present\"\"}, {\"\"w\",Fall 2024,Team-oriented transitional success 101"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 317
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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<product_listing>\n<product_id>PROD-110536</product_id>\n<name>Organized didactic parallelism</name>\n<category>clothing</category>\n<price>68.12</price>\n<currency>USD</currency>\n<stock>153</stock>\n<is_available>True</is_available>\n<rating>1.45</rating>\n<reviews>277</reviews>\n<specs>\n<weight_kg>1.85</weight_kg>\n<dimensions>33x70x14cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 180
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-3366717,Linda Clark,\"Anything music blood how public to. Even student idea piece if. Whom phone rich long.\nLook memory he\",Integrated bi-directional complexity,2026-01-07T13:19:20.433040,Tech,1143,\"[\"\"necessary\"\", \"\"listen\"\", \"\"employee\"\", \"\"here\"\"]\",75939\r\nART-2300982,Valerie Boyd,\"Certain individual something may.\nHome forget soldier send write voice above discuss. Environment de\",Reverse-engineered optimal paradigm,2026-01-06T10:45:06.021177,Business,3413,\"[\"\"poor\"\", \"\"there\"\", \"\"position\"\", \"\"simply\"\"]\",51647\r\nART-9981163,Anthony Evans,Letter tend while visit piece practice experience. Job month use my should weight local. Goal writer,Distributed client-server middleware,2026-01-03T06:40:27.860753,Tech,4279,\"[\"\"explain\"\", \"\"lay\"\", \"\"huge\"\", \"\"attention\"\", \"\"you\"\"]\",94849\r\nART-9931857,Calvin Allen,\"Back wrong central begin nation between how. Already see difference once they.\nJust bill true effort\",Organic zero tolerance approach,2026-01-07T09:32:14.685651,Business,4614,\"[\"\"street\"\", \"\"able\"\", \"\"option\"\"]\",21166\r\nART-4047081,Leonard Reynolds,Probably second front family within leg politics. Change conference argue market live fact developme,Team-oriented analyzing Graphical User Interface,2026-01-01T21:50:34.262728,Tech,3628,\"[\"\"couple\"\", \"\"idea\"\", \"\"appear\"\", \"\"let\"\", \"\"around\"\"]\",26508\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from CSV to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\narticle_id: ART-3366717\nheadline: Integrated bi-directional complexity\nauthor: Linda Clark\npublished: '2026-01-07T13:19:20.433040'\nsection: Tech\ncontent: 'Anything music blood how public to. Even student idea piece if. Whom phone\n rich long.\n\n Look memory help find reduce. Structure most tough realize ground.\n\n Around fear reduce ago. Thus moment letter evening stuff three.\n\n Her themselves campaign cup four catch as. Part turn leg.'\ntags:\n- necessary\n- listen\n- employee\n- here\nviews: 75939\nshares: 1143"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 207
}
|
[
{
"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 \"product_id\": \"PROD-141484\",\n \"name\": \"Managed bandwidth-monitored focus group\",\n \"category\": \"books\",\n \"price\": 751.35,\n \"currency\": \"USD\",\n \"stock\": 108,\n \"is_available\": true,\n \"rating\": 2.94,\n \"reviews\": 250,\n \"specs\": {\n \"weight_kg\": 6.41,\n \"dimensions\": \"15x82x35cm\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing 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<product_listing>\n<product_id>PROD-141484</product_id>\n<name>Managed bandwidth-monitored focus group</name>\n<category>books</category>\n<price>751.35</price>\n<currency>USD</currency>\n<stock>108</stock>\n<is_available>True</is_available>\n<rating>2.94</rating>\n<reviews>250</reviews>\n<specs>\n<weight_kg>6.41</weight_kg>\n<dimensions>15x82x35cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 183
}
|
[
{
"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<news_article>\n<article_id>ART-8846154</article_id>\n<headline>Phased bifurcated instruction set</headline>\n<author>Melanie Kennedy</author>\n<published>2026-01-02T14:27:49.190328</published>\n<section>Sports</section>\n<content>Edge wear coach whether dog sell respond. Claim feeling meeting somebody four real.\nIndeed use send represent leader require. Cup attack instead discuss. Plan with character rule.\nInformation mind company even serve. Experience pattern but certain she design speech.</content>\n<tags>memory</tags>\n<tags>score</tags>\n<tags>game</tags>\n<tags>join</tags>\n<views>47684</views>\n<shares>4081</shares>\n</news_article>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article 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 \"article_id\": \"ART-8846154\",\n \"headline\": \"Phased bifurcated instruction set\",\n \"author\": \"Melanie Kennedy\",\n \"published\": \"2026-01-02T14:27:49.190328\",\n \"section\": \"Sports\",\n \"content\": \"Edge wear coach whether dog sell respond. Claim feeling meeting somebody four real.\\nIndeed use send represent leader require. Cup attack instead discuss. Plan with character rule.\\nInformation mind company even serve. Experience pattern but certain she design speech.\",\n \"tags\": [\n \"memory\",\n \"score\",\n \"game\",\n \"join\"\n ],\n \"views\": 47684,\n \"shares\": 4081\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"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": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Visionary eco-centric methodology API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</edge>\n<get>\n<summary>Simple really social range.</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>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//edge>\n</paths>\n</api_specification>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification 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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Visionary eco-centric methodology API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/edge\": {\n \"get\": {\n \"summary\": \"Simple really social range.\",\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 \"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": "conversion",
"estimated_tokens": 245
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate news article data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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<news_article>\n<author>Jenna Bryant</author>\n<tags>most</tags>\n<tags>off</tags>\n<tags>shoulder</tags>\n<headline>Secured composite leverage</headline>\n<published>2026-01-04T22:19:16.750289</published>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 141
}
|
[
{
"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: 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:\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-485879,,CRS-1053,,2026-01-03,A,,,,,64.04,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 0, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 6, \"\"po\",STU-284737,,,89,exam\r\n,IWN240,CRS-4017,3,,,40,30,30,Beth Hoffman,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"happy\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"bit\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"camera\"\"}, {\"\"week\"\"\",,,Fall 2023,Pre-emptive client-driven groupware 101,,\r\n,VER341,CRS-8686,3,,,40,30,30,Lauren Avila,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"bag\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"society\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"partner\"\"}, {\"\"we\",,,Fall 2023,Distributed 4thgeneration strategy 101,,\r\n,JLD206,CRS-7575,4,,,40,30,30,Michael Rodriguez,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"during\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"traditional\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"example\"\"\",,,Fall 2022,Inverse radical collaboration 101,,"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 332
}
|
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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 \"article_id\": \"ART-3281345\",\n \"headline\": \"Streamlined object-oriented toolset\",\n \"author\": \"James Dunn\",\n \"published\": \"2026-01-03T08:23:33.060508\",\n \"section\": \"Politics\",\n \"content\": \"Win take among professor. Glass reflect black similar future. Risk than tree.\\nEconomic sit plan. Available then already skill up reason back. Course his threat growth physical parent truth.\\nLaugh article pull goal. Believe those few.\",\n \"tags\": [\n \"hit\",\n \"summer\",\n \"official\",\n \"rather\"\n ],\n \"views\": 75669,\n \"shares\": 293\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 212
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output research paper as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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:\npaper_id = \"arXiv:2024.49729\"\ntitle = \"Optimized fault-tolerant monitoring\"\nabstract = \"Relate make read game soldier new. Agree south attorney one century drive draw.\\nReduce head tax certainly offer deal. Sister station adult seat wear.\"\nkeywords = [ \"gas\", \"understand\", \"everything\", \"miss\",]\ncitations = 65\nfunding_source = \"Parsons Inc\"\n[[authors]]\nname = \"Ashley Hubbard\"\naffiliation = \"Mcdonald-White\"\nemail = \"jenniferlong@example.net\"\n\n[[authors]]\nname = \"Erica Marshall\"\naffiliation = \"Calderon-Dalton\"\nemail = \"adouglas@example.org\"\n\n[[authors]]\nname = \"Mercedes Campbell\"\naffiliation = \"Davis-Lynch\"\nemail = \"yharris@example.org\"\n\n[publication]\nvenue = \"Cell\"\nyear = 2024\ndoi = \"10.3465/hMKF\""
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"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": "Output financial report as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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<financial_report>\n<expenses>54498119</expenses>\n<ticker>OKCY</ticker>\n<company>Clark-Pearson</company>\n</financial_report>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 119
}
|
[
{
"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 \"company\": \"Smith-Glover\",\n \"ticker\": \"JROI\",\n \"quarter\": \"Q3 2023\",\n \"revenue\": 95238846,\n \"expenses\": 30652579,\n \"net_income\": 5856951,\n \"eps\": 7.31,\n \"metrics\": {\n \"profit_margin\": 9.94,\n \"roe\": 10.91\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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<financial_report>\n<company>Smith-Glover</company>\n<ticker>JROI</ticker>\n<quarter>Q3 2023</quarter>\n<revenue>95238846</revenue>\n<expenses>30652579</expenses>\n<net_income>5856951</net_income>\n<eps>7.31</eps>\n<metrics>\n<profit_margin>9.94</profit_margin>\n<roe>10.91</roe>\n</metrics>\n</financial_report>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 163
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output api specification as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Intuitive disintermediate website API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/reality\": {\n \"get\": {\n \"summary\": \"Activity public whole paper there relationship tas\",\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 \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 249
}
|
End of preview. Expand
in Data Studio
No dataset card yet
- Downloads last month
- 9