u-10bei/unsloth_qwen3-4binst_cot5_e1_merged
Text Generation
•
4B
•
Updated
•
14
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": "Produce a TOML document for a api specification."
},
{
"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 = \"Face-to-face dedicated model API\"\nversion = \"1.0.0\"\n\n[paths.\"/pay\".get]\nsummary = \"Up very certain bad scientist management.\"\n[[paths.\"/pay\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/pay\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/pay\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/pay\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 184
}
|
[
{
"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 \"article_id\": \"ART-1413987\",\n \"headline\": \"Operative fault-tolerant hierarchy\",\n \"author\": \"Angela Adams\",\n \"published\": \"2026-01-01T22:25:46.165476\",\n \"section\": \"Politics\",\n \"content\": \"Message they tax policy start result. Fine body receive.\\nEasy in during stock not school. Morning score case avoid energy.\\nNorth general get charge miss similar lead. Whole research produce source Republican.\",\n \"tags\": [\n \"bill\",\n \"else\",\n \"special\"\n ],\n \"views\": 38349,\n \"shares\": 3405\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article 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<news_article>\n<article_id>ART-1413987</article_id>\n<headline>Operative fault-tolerant hierarchy</headline>\n<author>Angela Adams</author>\n<published>2026-01-01T22:25:46.165476</published>\n<section>Politics</section>\n<content>Message they tax policy start result. Fine body receive.\nEasy in during stock not school. Morning score case avoid energy.\nNorth general get charge miss similar lead. Whole research produce source Republican.</content>\n<tags>bill</tags>\n<tags>else</tags>\n<tags>special</tags>\n<views>38349</views>\n<shares>3405</shares>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 228
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output financial report as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexpenses: 7264503\nquarter: Q3 2024\nticker: BKUX\ncompany: Sanchez and Sons\nnet_income: 18666942\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 103
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate customer review data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate: '2026-01-06'\nuser_id: a66012bb-d947-4473-920b-f95bb71a9d4b\ncontent: 'But raise animal four painting do. Her sea find clearly discussion state.\n\n Continue people bad move film property.\n\n Defense picture Mrs that building look ahead. Late my since project.'\ntitle: Say they owner collection expert.\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 155
}
|
[
{
"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,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/trade_get_parameters,paths_/trade_get_responses_200_description,paths_/trade_get_responses_400_description,paths_/trade_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Extended national database API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,If skin together police leave themselves.,,,,\r\nSmall leader far picture here Mrs long. Agency or choose.,\"[{\"\"name\"\": \"\"Samuel Brown\"\", \"\"affiliation\"\": \"\"Williamson-Davis\"\", \"\"email\"\": \"\"brownjeffrey@example.org\"\"}, {\",278,None,,,\"[\"\"management\"\", \"\"against\"\", \"\"section\"\"]\",,arXiv:2022.52164,,,,,10.5855/BsOq,Cell,2021,Focused 3rdgeneration standardization\r\n\"Century meet society though part. Many red benefit human PM nor unit these.\nSing time door Mr whethe\",\"[{\"\"name\"\": \"\"Cheryl Santos\"\", \"\"affiliation\"\": \"\"Kelly, French and Wheeler\"\", \"\"email\"\": \"\"gregoryerik@example\",37,None,,,\"[\"\"which\"\", \"\"painting\"\", \"\"their\"\", \"\"sing\"\"]\",,arXiv:2020.29260,,,,,10.1067/JkdG,Nature,2023,Synergistic grid-enabled standardization\r\nImprove billion factor cause which think. Party put reduce himself.,\"[{\"\"name\"\": \"\"Jessica Harper\"\", \"\"affiliation\"\": \"\"Moore-Jenkins\"\", \"\"email\"\": \"\"nicholascarter@example.org\"\"}, \",56,Bowman-Brooks,,,\"[\"\"defense\"\", \"\"culture\"\", \"\"second\"\", \"\"air\"\", \"\"meeting\"\"]\",,arXiv:2024.34573,,,,,10.5922/PAsu,Cell,2020,Sharable zero-defect utilization\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Extended national database API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</trade>\n<get>\n<summary>If skin together police leave themselves.</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<//trade>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 226
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"company\": \"Perez-Davis\",\n \"ticker\": \"BXTK\",\n \"quarter\": \"Q3 2021\",\n \"revenue\": 81704268,\n \"expenses\": 35155875,\n \"net_income\": 15488385,\n \"eps\": 8.42,\n \"metrics\": {\n \"profit_margin\": 5.82,\n \"roe\": 7.77\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 134
}
|
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\nGovernment maybe customer likely assume require none. As service ahead avoid.,,,None,,,,,,Managed next generation success\r\n\"Whatever add attack pick us. During meet face structure.\nYear stay box ability. Time example kind. L\",\"[{\"\"name\"\": \"\"Jason Garcia\"\", \"\"affiliation\"\": \"\"Weber, Richard and Martinez\"\", \"\"email\"\": \"\"kwallace@example.o\",26,Robinson-Rice,\"[\"\"information\"\", \"\"quality\"\", \"\"worker\"\", \"\"season\"\", \"\"especially\"\"]\",arXiv:2023.98703,10.7206/NhXp,Cell,2022,Diverse high-level hub\r\nAlready choose win difficult. History people although reduce would. Reflect great goal while.,\"[{\"\"name\"\": \"\"Chelsea Lutz\"\", \"\"affiliation\"\": \"\"Lopez PLC\"\", \"\"email\"\": \"\"ashley11@example.org\"\"}, {\"\"name\"\": \"\"Jo\",449,None,\"[\"\"fine\"\", \"\"building\"\", \"\"central\"\", \"\"strategy\"\"]\",arXiv:2022.64065,10.2641/XoGu,Nature,2020,Profit-focused multimedia service-desk\r\nEverybody own land measure future participant early.,\"[{\"\"name\"\": \"\"Zachary Hines\"\", \"\"affiliation\"\": \"\"Newton-Miller\"\", \"\"email\"\": \"\"frazierchristine@example.com\"\"},\",54,None,\"[\"\"race\"\", \"\"lead\"\", \"\"then\"\"]\",arXiv:2024.20385,10.3551/bmDm,Nature,2021,Robust static knowledgebase\r\nPeople character gun partner avoid cold believe appear. Civil dark thousand police.,\"[{\"\"name\"\": \"\"Brittany Collier\"\", \"\"affiliation\"\": \"\"Hunt Inc\"\", \"\"email\"\": \"\"wsampson@example.org\"\"}, {\"\"name\"\": \",492,Fisher Ltd,\"[\"\"movie\"\", \"\"so\"\", \"\"yeah\"\"]\",arXiv:2021.88233,10.8501/BfhU,Science,2021,Up-sized 4thgeneration software\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 471
}
|
[
{
"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<social_media_post>\n<platform>twitter</platform>\n<content>For garden your position. Audience care state law.\nAny easy coach ability four term. Former age rest east real group.</content>\n<timestamp>2026-01-20T00:31:35.082107</timestamp>\n<hashtags>#next</hashtags>\n<hashtags>#artist</hashtags>\n<hashtags>#behavior</hashtags>\n<username>davisalyssa</username>\n</social_media_post>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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 \"platform\": \"twitter\",\n \"content\": \"For garden your position. Audience care state law.\\nAny easy coach ability four term. Former age rest east real group.\",\n \"timestamp\": \"2026-01-20T00:31:35.082107\",\n \"hashtags\": [\n \"#next\",\n \"#artist\",\n \"#behavior\"\n ],\n \"username\": \"davisalyssa\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 156
}
|
[
{
"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\": \"Ramirez PLC\",\n \"ticker\": \"RTTW\",\n \"quarter\": \"Q1 2020\",\n \"revenue\": 19940548,\n \"expenses\": 33463500,\n \"net_income\": 10979677,\n \"eps\": 3.8,\n \"metrics\": {\n \"profit_margin\": 18.45,\n \"roe\": 22.81\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<financial_report>\n<company>Ramirez PLC</company>\n<ticker>RTTW</ticker>\n<quarter>Q1 2020</quarter>\n<revenue>19940548</revenue>\n<expenses>33463500</expenses>\n<net_income>10979677</net_income>\n<eps>3.8</eps>\n<metrics>\n<profit_margin>18.45</profit_margin>\n<roe>22.81</roe>\n</metrics>\n</financial_report>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 164
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this YAML data into XML format:\nproduct_id: PROD-245020\nname: Open-architected 3rdgeneration orchestration\ncategory: electronics\nprice: 143.86\ncurrency: USD\nstock: 24\nis_available: true\nrating: 3.01\nreviews: 584\nspecs:\n weight_kg: 27.61\n dimensions: 42x62x84cm\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from YAML 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<product_listing>\n<product_id>PROD-245020</product_id>\n<name>Open-architected 3rdgeneration orchestration</name>\n<category>electronics</category>\n<price>143.86</price>\n<currency>USD</currency>\n<stock>24</stock>\n<is_available>True</is_available>\n<rating>3.01</rating>\n<reviews>584</reviews>\n<specs>\n<weight_kg>27.61</weight_kg>\n<dimensions>42x62x84cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 186
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: 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 \"units_sold\": 77351,\n \"top_products\": [\n {\n \"sku\": \"SKU-1310\",\n \"sales\": 347309\n },\n {\n \"sku\": \"SKU-4934\",\n \"sales\": 155694\n },\n {\n \"sku\": \"SKU-6309\",\n \"sales\": 80805\n }\n ],\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 1289255,\n \"growth\": 34.17\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 1203582,\n \"growth\": 26.83\n }\n ],\n \"period\": \"March 2024\",\n \"total_revenue\": 6355580\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 197
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"contract_id\": \"CTR-169518\",\n \"parties\": [\n {\n \"name\": \"Robinson-Holmes\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Barker, Morgan and Griffith\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-10\",\n \"term_months\": 40,\n \"value\": 683910,\n \"status\": \"pending\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-169518</contract_id>\n<parties>\n<name>Robinson-Holmes</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Barker, Morgan and Griffith</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-10</effective_date>\n<term_months>40</term_months>\n<value>683910</value>\n<status>pending</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 170
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output transaction record as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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 \"txn_id\": \"TXN-71367496\",\n \"customer_id\": \"49fa7bcb-94f8-41f2-bfb8-e3c7eddb477e\",\n \"timestamp\": \"2026-01-20T00:31:35.390291\",\n \"items\": [\n {\n \"sku\": \"SKU-57836\",\n \"qty\": 2,\n \"price\": 144.52\n }\n ],\n \"subtotal\": 1083.15,\n \"tax\": 15.11,\n \"total\": 1907.96,\n \"payment_method\": \"apple_pay\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 158
}
|
[
{
"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 \"product_id\": \"PROD-727346\",\n \"name\": \"Triple-buffered contextually-based protocol\",\n \"category\": \"electronics\",\n \"price\": 425.99,\n \"currency\": \"USD\",\n \"stock\": 856,\n \"is_available\": true,\n \"rating\": 2.25,\n \"reviews\": 79,\n \"specs\": {\n \"weight_kg\": 9.08,\n \"dimensions\": \"84x59x50cm\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing 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<product_listing>\n<product_id>PROD-727346</product_id>\n<name>Triple-buffered contextually-based protocol</name>\n<category>electronics</category>\n<price>425.99</price>\n<currency>USD</currency>\n<stock>856</stock>\n<is_available>True</is_available>\n<rating>2.25</rating>\n<reviews>79</reviews>\n<specs>\n<weight_kg>9.08</weight_kg>\n<dimensions>84x59x50cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 186
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following CSV to TOML:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/old_get_parameters,paths_/old_get_responses_200_description,paths_/old_get_responses_400_description,paths_/old_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Mandatory executive instruction set API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Government stage west it.,,,,\r\n\"Guy stop professor series room. Watch star my blue yes.\nIssue kid sort once. Step police edge team c\",\"[{\"\"name\"\": \"\"Mrs. Jennifer Soto MD\"\", \"\"affiliation\"\": \"\"West, Morgan and Wagner\"\", \"\"email\"\": \"\"thomas19@exam\",142,None,,,\"[\"\"pressure\"\", \"\"action\"\", \"\"something\"\", \"\"mind\"\"]\",,arXiv:2024.92751,,,,,10.4192/Esot,Nature,2022,Open-source 5thgeneration middleware\r\nHit can science himself sometimes. Their laugh task security behavior wind fill.,\"[{\"\"name\"\": \"\"Jerry Chavez\"\", \"\"affiliation\"\": \"\"Stevens, Davis and Flores\"\", \"\"email\"\": \"\"lindsey51@example.ne\",16,\"Peck, Pugh and Jackson\",,,\"[\"\"recent\"\", \"\"last\"\", \"\"month\"\", \"\"commercial\"\", \"\"choose\"\"]\",,arXiv:2022.45042,,,,,10.7573/tYUR,Science,2024,Grass-roots user-facing artificial intelligence\r\n\"Tv now officer. Different measure instead apply. Minute good question.\nPublic condition individual w\",\"[{\"\"name\"\": \"\"Shelly Hudson\"\", \"\"affiliation\"\": \"\"Smith-Adams\"\", \"\"email\"\": \"\"njones@example.net\"\"}, {\"\"name\"\": \"\"N\",222,\"Reynolds, Harmon and Stafford\",,,\"[\"\"eight\"\", \"\"member\"\", \"\"power\"\"]\",,arXiv:2021.10224,,,,,10.5394/tqBf,Cell,2020,Front-line high-level function\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from CSV to 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. Transform values to match the target format specifications.\n\nOutput:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Mandatory executive instruction set API\"\nversion = \"1.0.0\"\n\n[paths.\"/old\".get]\nsummary = \"Government stage west it.\"\n[[paths.\"/old\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/old\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/old\".get.parameters]]\nname = \"param2\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/old\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/old\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 202
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in XML\n2. Complexity: 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<sales_analytics>\n<period>January 2021</period>\n<total_revenue>5093448</total_revenue>\n<units_sold>51650</units_sold>\n<channels>\n<name>retail</name>\n<revenue>2801029</revenue>\n<growth>13.26</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>4933419</revenue>\n<growth>26.19</growth>\n</channels>\n<top_products>\n<sku>SKU-6023</sku>\n<sales>481346</sales>\n</top_products>\n<top_products>\n<sku>SKU-9484</sku>\n<sales>32588</sales>\n</top_products>\n<top_products>\n<sku>SKU-1138</sku>\n<sales>33897</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 221
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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<experiment_result>\n<experiment_id>EXP-550210</experiment_id>\n<title>Effect of lawyer on toward</title>\n<methodology>\n<design>cohort</design>\n<sample_size>368</sample_size>\n<duration_days>90</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>26.63</baseline>\n<endpoint>83.5</endpoint>\n<p_value>0.0519</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>88.01</baseline>\n<endpoint>89.71</endpoint>\n<p_value>0.3105</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"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 \"contract_id\": \"CTR-617878\",\n \"parties\": [\n {\n \"name\": \"Martin-Kelley\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Miller, Flores and Smith\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-16\",\n \"term_months\": 20,\n \"value\": 46161,\n \"status\": \"pending\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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<contract>\n<contract_id>CTR-617878</contract_id>\n<parties>\n<name>Martin-Kelley</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Miller, Flores and Smith</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-16</effective_date>\n<term_months>20</term_months>\n<value>46161</value>\n<status>pending</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 169
}
|
[
{
"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<paths>\n</language>\n<get>\n<summary>Same own admit perform high.</summary>\n<parameters>\n<name>param0</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<//language>\n</paths>\n<info>\n<title>Function-based intermediate Local Area Network API</title>\n<version>1.0.0</version>\n</info>\n<openapi>3.0.0</openapi>\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 \"paths\": {\n \"/language\": {\n \"get\": {\n \"summary\": \"Same own admit perform high.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\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 \"info\": {\n \"title\": \"Function-based intermediate Local Area Network API\",\n \"version\": \"1.0.0\"\n },\n \"openapi\": \"3.0.0\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 222
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-1239438</review_id>\n<product_id>PROD-687452</product_id>\n<user_id>a1299248-5060-42f3-a1be-7c0c98ac8801</user_id>\n<rating>4</rating>\n<title>Money both attorney carry.</title>\n<content>Catch remain rise job change single. Fly certainly finish try buy between. Poor often son view capital occur consumer line.\nEnter doctor read significant area attorney.</content>\n<date>2026-01-09</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>41</helpful_votes>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-1239438\",\n \"product_id\": \"PROD-687452\",\n \"user_id\": \"a1299248-5060-42f3-a1be-7c0c98ac8801\",\n \"rating\": 4,\n \"title\": \"Money both attorney carry.\",\n \"content\": \"Catch remain rise job change single. Fly certainly finish try buy between. Poor often son view capital occur consumer line.\\nEnter doctor read significant area attorney.\",\n \"date\": \"2026-01-09\",\n \"verified_purchase\": true,\n \"helpful_votes\": 41\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 188
}
|
[
{
"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 TOML to JSON:\npatient_mrn = \"MRN-400292\"\ndate = \"2026-01-12\"\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"20mg\"\nfrequency = \"BID\"\nquantity = 30\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 60\n\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 90\n\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from TOML 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 \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"BID\",\n \"quantity\": 60\n },\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"5mg\",\n \"frequency\": \"BID\",\n \"quantity\": 90\n }\n ],\n \"patient_mrn\": \"MRN-400292\",\n \"date\": \"2026-01-12\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "prescription",
"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": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-697767</contract_id>\n<parties>\n<name>Hicks, Johnson and Hamilton</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Garcia and Sons</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-07</effective_date>\n<term_months>16</term_months>\n<value>126137</value>\n<status>executed</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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 \"contract_id\": \"CTR-697767\",\n \"parties\": [\n {\n \"name\": \"Hicks, Johnson and Hamilton\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Garcia and Sons\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-07\",\n \"term_months\": 16,\n \"value\": 126137,\n \"status\": \"executed\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"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": "Output api specification as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Business-focused composite contingency API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</inside>\n<get>\n<summary>Compare know economic thus.</summary>\n<parameters>\n<name>param0</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<//inside>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 205
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate error log data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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<error_log>\n<error_id>528164f4-6176-4d78-87df-47148baac7df</error_id>\n<timestamp>2026-01-20T00:31:33.457419</timestamp>\n<level>ERROR</level>\n<service>passService</service>\n<message>Federal arrive much.</message>\n<stack_trace>at drug.py:154</stack_trace>\n<stack_trace>at class.py:28</stack_trace>\n<stack_trace>at base.py:181</stack_trace>\n<stack_trace>at tend.py:175</stack_trace>\n<context>\n<user_id>9602fb41-8841-4f71-b5b3-87fd32e24098</user_id>\n<request_id>2b2258f9-f9cc-4b71-91ad-31b7a35f5d5f</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 218
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the data below from CSV to TOML:\ncontract_id,effective_date,parties,status,term_months,value\r\nCTR-681513,2026-01-15,\"[{\"\"name\"\": \"\"Snyder Ltd\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Carlson-Lopez\"\", \"\"role\"\": \"\"party_b\"\"}]\",executed,21,885678\r\nCTR-188237,2026-01-16,\"[{\"\"name\"\": \"\"Hickman Inc\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Rodriguez, Andrews and Lindsey\"\", \"\"role\"\": \"\"par\",executed,20,487125\r\nCTR-139022,2026-01-07,\"[{\"\"name\"\": \"\"Vaughn-Roman\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Hansen-Kane\"\", \"\"role\"\": \"\"party_b\"\"}]\",active,41,57241\r\nCTR-257976,2026-01-05,\"[{\"\"name\"\": \"\"Keller-Clark\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Jones-Ferguson\"\", \"\"role\"\": \"\"party_b\"\"}]\",executed,35,425078\r\nCTR-437159,2026-01-14,\"[{\"\"name\"\": \"\"Wu, Rios and Mclaughlin\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Martin, Murphy and Sanchez\"\", \"\"rol\",pending,19,582535\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from CSV to 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. Transform values to match the target format specifications.\n\nOutput:\ncontract_id = \"CTR-681513\"\neffective_date = \"2026-01-15\"\nterm_months = 21\nvalue = 885678\nstatus = \"executed\"\n[[parties]]\nname = \"Snyder Ltd\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Carlson-Lopez\"\nrole = \"party_b\"\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 126
}
|
[
{
"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 TOML to JSON:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Multi-lateral demand-driven matrices API\"\nversion = \"1.0.0\"\n\n[paths.\"/speech\".get]\nsummary = \"According institution everybody bad listen nearly.\"\n[[paths.\"/speech\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/speech\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/speech\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/speech\".get.responses.400]\ndescription = \"Bad Request\"\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from TOML 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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Multi-lateral demand-driven matrices API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/speech\": {\n \"get\": {\n \"summary\": \"According institution everybody bad listen nearly.\",\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": "conversion",
"estimated_tokens": 251
}
|
[
{
"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\": \"Open-source stable circuit API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/like\": {\n \"get\": {\n \"summary\": \"Adult religious day end easy nation discover optio\",\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>Open-source stable circuit API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</like>\n<get>\n<summary>Adult religious day end easy nation discover optio</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<//like>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 228
}
|
[
{
"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>Expanded real-time emulation API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</whom>\n<get>\n<summary>Question rather summer same simple first able.</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<//whom>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 247
}
|
[
{
"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: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"course_id\": \"CRS-6893\",\n \"code\": \"EUO309\",\n \"title\": \"Realigned clear-thinking solution 101\",\n \"instructor\": \"Carrie Arnold\",\n \"credits\": 4,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"everything\"\n },\n {\n \"week\": 2,\n \"topic\": \"east\"\n },\n {\n \"week\": 3,\n \"topic\": \"yes\"\n },\n {\n \"week\": 4,\n \"topic\": \"green\"\n },\n {\n \"week\": 5,\n \"topic\": \"she\"\n },\n {\n \"week\": 6,\n \"topic\": \"decide\"\n },\n {\n \"week\": 7,\n \"topic\": \"message\"\n },\n {\n \"week\": 8,\n \"topic\": \"after\"\n },\n {\n \"week\": 9,\n \"topic\": \"throw\"\n },\n {\n \"week\": 10,\n \"topic\": \"change\"\n },\n {\n \"week\": 11,\n \"topic\": \"character\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 293
}
|
[
{
"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: 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 \"article_id\": \"ART-6533186\",\n \"headline\": \"Open-source methodical Graphical User Interface\",\n \"author\": \"Kelly Robinson\",\n \"published\": \"2026-01-11T19:52:58.402021\",\n \"section\": \"Politics\",\n \"content\": \"Product question make later during stage power of. Gas according skin decision space those environmental. Into answer others pattern believe listen. Hand voice end any different company.\\nCup affect management cut hot people. Station office late manager forget discover.\",\n \"tags\": [\n \"language\",\n \"involve\",\n \"store\",\n \"doctor\",\n \"job\"\n ],\n \"views\": 84925,\n \"shares\": 2572\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 229
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output news article as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-1449516,Mary Benitez,\"Above crime doctor paper onto who scientist. Me news last able.\nCurrent director visit recently the.\",Right-sized well-modulated infrastructure,2026-01-19T16:23:59.933315,Politics,4564,\"[\"\"training\"\", \"\"away\"\", \"\"me\"\", \"\"specific\"\", \"\"central\"\"]\",24706\r\nART-7684491,Laura Murphy,\"Accept my capital build. Summer policy decision debate.\nBody again play learn. He glass economy agre\",Phased zero tolerance instruction set,2026-01-07T08:50:46.440999,Tech,1253,\"[\"\"model\"\", \"\"tend\"\", \"\"hair\"\", \"\"behind\"\"]\",57030\r\nART-2776052,Elizabeth Preston,\"Discover tend peace expect. Kind onto design.\nHimself test painting himself.\nGuess say arm strategy \",Inverse leadingedge project,2026-01-18T19:12:01.221709,Sports,1597,\"[\"\"safe\"\", \"\"president\"\", \"\"laugh\"\"]\",79695\r\nART-7361357,Richard Brown,\"Road human really. Civil apply anyone idea. Direction officer local either save present.\nMeeting hol\",Vision-oriented 24hour standardization,2026-01-12T05:47:02.926279,Business,2996,\"[\"\"three\"\", \"\"sound\"\", \"\"which\"\", \"\"together\"\"]\",39218\r\nART-8179187,Jeremy Allen,\"Job be ability fast nor happen. Car provide carry which receive on.\nMean in around. Group drop where\",Centralized upward-trending orchestration,2026-01-15T01:22:03.194712,Business,3868,\"[\"\"agreement\"\", \"\"weight\"\", \"\"factor\"\", \"\"term\"\", \"\"help\"\"]\",69843\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 426
}
|
[
{
"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<research_paper>\n<paper_id>arXiv:2021.38474</paper_id>\n<title>Synergized optimizing solution</title>\n<authors>\n<name>Kristin Stein</name>\n<affiliation>Mcdonald-Holden</affiliation>\n<email>christine14@example.com</email>\n</authors>\n<authors>\n<name>Jeffrey Richards</name>\n<affiliation>Owens and Sons</affiliation>\n<email>ijones@example.org</email>\n</authors>\n<abstract>Explain reduce believe show. Wrong through station explain run.</abstract>\n<keywords>north</keywords>\n<keywords>American</keywords>\n<keywords>team</keywords>\n<keywords>ability</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2022</year>\n<doi>10.6121/ozCS</doi>\n</publication>\n<citations>228</citations>\n<funding_source>Byrd-Davis</funding_source>\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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 \"paper_id\": \"arXiv:2021.38474\",\n \"title\": \"Synergized optimizing solution\",\n \"authors\": [\n {\n \"name\": \"Kristin Stein\",\n \"affiliation\": \"Mcdonald-Holden\",\n \"email\": \"christine14@example.com\"\n },\n {\n \"name\": \"Jeffrey Richards\",\n \"affiliation\": \"Owens and Sons\",\n \"email\": \"ijones@example.org\"\n }\n ],\n \"abstract\": \"Explain reduce believe show. Wrong through station explain run.\",\n \"keywords\": [\n \"north\",\n \"American\",\n \"team\",\n \"ability\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2022,\n \"doi\": \"10.6121/ozCS\"\n },\n \"citations\": 228,\n \"funding_source\": \"Byrd-Davis\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 241
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-1413987,Angela Adams,\"Message they tax policy start result. Fine body receive.\nEasy in during stock not school. Morning sc\",Operative fault-tolerant hierarchy,2026-01-01T22:25:46.165476,Politics,3405,\"[\"\"bill\"\", \"\"else\"\", \"\"special\"\"]\",38349\r\nART-5954239,Kevin Collins,\"Plant room Mrs present. Any red short peace author realize. Box goal eight but morning me.\nCultural \",Progressive bi-directional application,2026-01-11T21:56:44.587435,Tech,620,\"[\"\"reach\"\", \"\"method\"\", \"\"growth\"\"]\",51983\r\nART-5390176,Samuel Payne,\"Some field create write.\nArgue here somebody big throw first. Beautiful but sit college. Night call \",Switchable dedicated ability,2026-01-10T17:09:00.629545,Sports,3316,\"[\"\"see\"\", \"\"third\"\", \"\"might\"\", \"\"past\"\", \"\"up\"\"]\",39944\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 282
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<context>\n<user_id>f5f352cd-19d2-4ab0-a545-553150c73696</user_id>\n<request_id>b16f3695-6899-48b8-afe7-474751f075eb</request_id>\n</context>\n<message>Network under picture station face.</message>\n<error_id>91b5143a-d690-49a8-818a-e8751267da23</error_id>\n<service>civilService</service>\n<stack_trace>at sport.py:202</stack_trace>\n<stack_trace>at various.py:145</stack_trace>\n<stack_trace>at between.py:378</stack_trace>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"context\": {\n \"user_id\": \"f5f352cd-19d2-4ab0-a545-553150c73696\",\n \"request_id\": \"b16f3695-6899-48b8-afe7-474751f075eb\"\n },\n \"message\": \"Network under picture station face.\",\n \"error_id\": \"91b5143a-d690-49a8-818a-e8751267da23\",\n \"service\": \"civilService\",\n \"stack_trace\": [\n \"at sport.py:202\",\n \"at various.py:145\",\n \"at between.py:378\"\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 170
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-804184</contract_id>\n<parties>\n<name>Stewart LLC</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Romero-Barker</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-19</effective_date>\n<term_months>40</term_months>\n<value>854585</value>\n<status>executed</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 165
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following JSON to TOML:\n{\n \"contract_id\": \"CTR-877527\",\n \"parties\": [\n {\n \"name\": \"Schmidt and Sons\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Hoover, Dyer and Hunter\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-15\",\n \"term_months\": 32,\n \"value\": 395930,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to 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. Transform values to match the target format specifications.\n\nOutput:\ncontract_id = \"CTR-877527\"\neffective_date = \"2026-01-15\"\nterm_months = 32\nvalue = 395930\nstatus = \"active\"\n[[parties]]\nname = \"Schmidt and Sons\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Hoover, Dyer and Hunter\"\nrole = \"party_b\"\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 130
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\nStanton-Ward,7.61,21257983,22.01,9.95,6319972,Q4 2022,42962486,GANN\r\nLong Ltd,2.6,19180251,29.59,21.6,1118708,Q2 2020,31816480,QDXG\r\n\"Lopez, Johnson and Johnson\",4.4,53963532,12.22,5.15,16125450,Q3 2024,8097276,QYIE\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 154
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output product listing as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: 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 \"reviews\": 593,\n \"price\": 170.91,\n \"name\": \"Fundamental clear-thinking project\",\n \"stock\": 810,\n \"rating\": 1.79\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 109
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate social media post data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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<social_media_post>\n<post_id>POST-87183909</post_id>\n<platform>twitter</platform>\n<user_id>6fb59d0d-6ee8-4546-8c2b-dabb2d1e0269</user_id>\n<username>acastillo</username>\n<content>Finish of finally process level experience for.\nDark health week marriage. Nature fly seat chair watch avoid. Seat country key necessary now.</content>\n<timestamp>2026-01-20T00:31:34.171576</timestamp>\n<hashtags>#door</hashtags>\n<hashtags>#really</hashtags>\n<engagement>\n<likes>6884</likes>\n<shares>669</shares>\n<comments>15</comments>\n</engagement>\n</social_media_post>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"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": "Generate error log data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id = \"52d03157-3fa6-4e42-9128-cbffdade2acf\"\nstack_trace = [ \"at mean.py:270\", \"at eight.py:325\",]\ntimestamp = \"2026-01-20T00:31:34.248566\"\n\n[context]\nuser_id = \"f2949768-f5c0-4ab6-a8f5-3ef0d3b039c7\"\nrequest_id = \"0782b862-4e67-4eb6-80ed-30e1f190af01\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 138
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output transaction record as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn_id>TXN-59190782</txn_id>\n<customer_id>65e8a365-1ba2-467e-9d40-f5f5273b8767</customer_id>\n<timestamp>2026-01-20T00:31:35.829895</timestamp>\n<items>\n<sku>SKU-54397</sku>\n<qty>2</qty>\n<price>372.2</price>\n</items>\n<items>\n<sku>SKU-30694</sku>\n<qty>3</qty>\n<price>144.58</price>\n</items>\n<items>\n<sku>SKU-37334</sku>\n<qty>4</qty>\n<price>367.05</price>\n</items>\n<items>\n<sku>SKU-24496</sku>\n<qty>2</qty>\n<price>331.57</price>\n</items>\n<subtotal>716.8</subtotal>\n<tax>162.16</tax>\n<total>2113.17</total>\n<payment_method>paypal</payment_method>\n</transaction_record>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 234
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"period\": \"August 2023\",\n \"total_revenue\": 8405692,\n \"units_sold\": 76034,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 4383553,\n \"growth\": 30.16\n },\n {\n \"name\": \"retail\",\n \"revenue\": 2042295,\n \"growth\": -5.01\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6460\",\n \"sales\": 49937\n },\n {\n \"sku\": \"SKU-8481\",\n \"sales\": 236379\n },\n {\n \"sku\": \"SKU-8306\",\n \"sales\": 164100\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>August 2023</period>\n<total_revenue>8405692</total_revenue>\n<units_sold>76034</units_sold>\n<channels>\n<name>online</name>\n<revenue>4383553</revenue>\n<growth>30.16</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>2042295</revenue>\n<growth>-5.01</growth>\n</channels>\n<top_products>\n<sku>SKU-6460</sku>\n<sales>49937</sales>\n</top_products>\n<top_products>\n<sku>SKU-8481</sku>\n<sales>236379</sales>\n</top_products>\n<top_products>\n<sku>SKU-8306</sku>\n<sales>164100</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 CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the data below from JSON to CSV:\n{\n \"period\": \"November 2022\",\n \"total_revenue\": 6343574,\n \"units_sold\": 17398,\n \"channels\": [\n {\n \"name\": \"retail\",\n \"revenue\": 4047175,\n \"growth\": -0.13\n },\n {\n \"name\": \"online\",\n \"revenue\": 2586932,\n \"growth\": 31.36\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-9124\",\n \"sales\": 47753\n },\n {\n \"sku\": \"SKU-5049\",\n \"sales\": 248155\n },\n {\n \"sku\": \"SKU-8985\",\n \"sales\": 113817\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from JSON 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:\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\"\": \"\"retail\"\", \"\"revenue\"\": 4047175, \"\"growth\"\": -0.13}, {\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 2586932, \"\"gr\",,,,,November 2022,,,,,\"[{\"\"sku\"\": \"\"SKU-9124\"\", \"\"sales\"\": 47753}, {\"\"sku\"\": \"\"SKU-5049\"\", \"\"sales\"\": 248155}, {\"\"sku\"\": \"\"SKU-8985\"\", \"\"sal\",6343574,17398\r\nRoad fight federal night experience operation. Dinner middle support different may where part detail,\"[{\"\"name\"\": \"\"Mark Thomas\"\", \"\"affiliation\"\": \"\"Davis Ltd\"\", \"\"email\"\": \"\"christinaharrison@example.com\"\"}, {\"\"na\",,227,None,\"[\"\"wide\"\", \"\"instead\"\", \"\"week\"\", \"\"thing\"\", \"\"nature\"\"]\",arXiv:2022.81609,,10.4534/YoGq,Cell,2024,Proactive content-based hub,,,\r\nCondition risk beat anything respond. Than mention artist key black send present. Budget water every,\"[{\"\"name\"\": \"\"Benjamin Richardson\"\", \"\"affiliation\"\": \"\"Preston, Hill and Anderson\"\", \"\"email\"\": \"\"jmiller@exam\",,471,Fleming Ltd,\"[\"\"marriage\"\", \"\"out\"\", \"\"south\"\", \"\"north\"\", \"\"hear\"\"]\",arXiv:2022.54447,,10.4421/WPgK,Nature,2021,Enhanced homogeneous moratorium,,,\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 373
}
|
[
{
"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 \"error_id\": \"5463a9f8-039d-47b6-a982-4552b0e18149\",\n \"timestamp\": \"2026-01-20T00:31:34.089906\",\n \"level\": \"WARNING\",\n \"service\": \"carryService\",\n \"message\": \"Education play property price one.\",\n \"stack_trace\": [\n \"at table.py:130\",\n \"at general.py:387\",\n \"at professor.py:324\"\n ],\n \"context\": {\n \"user_id\": \"d0fa20ad-2e26-4ef3-865f-d919a467689f\",\n \"request_id\": \"ff10c83f-a59a-4a01-92c4-7c7e7716841e\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log 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<error_log>\n<error_id>5463a9f8-039d-47b6-a982-4552b0e18149</error_id>\n<timestamp>2026-01-20T00:31:34.089906</timestamp>\n<level>WARNING</level>\n<service>carryService</service>\n<message>Education play property price one.</message>\n<stack_trace>at table.py:130</stack_trace>\n<stack_trace>at general.py:387</stack_trace>\n<stack_trace>at professor.py:324</stack_trace>\n<context>\n<user_id>d0fa20ad-2e26-4ef3-865f-d919a467689f</user_id>\n<request_id>ff10c83f-a59a-4a01-92c4-7c7e7716841e</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 216
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-540153</contract_id>\n<parties>\n<name>Larson-Watkins</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Anderson-Rogers</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-04</effective_date>\n<term_months>17</term_months>\n<value>561671</value>\n<status>executed</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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 \"contract_id\": \"CTR-540153\",\n \"parties\": [\n {\n \"name\": \"Larson-Watkins\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Anderson-Rogers\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-04\",\n \"term_months\": 17,\n \"value\": 561671,\n \"status\": \"executed\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 149
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output news article as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\narticle_id = \"ART-7580794\"\nheadline = \"Persistent neutral complexity\"\nauthor = \"Bryan Mack\"\npublished = \"2026-01-04T23:49:42.858494\"\nsection = \"Politics\"\ncontent = \"Understand measure hand major stay section. Series floor fish wind hold policy. Family various left administration environment body.\\nDrug note but condition remain. Watch attention entire site. Else first ask policy place do current. Standard professional man actually own east agent.\"\ntags = [ \"its\", \"other\", \"coach\", \"remain\",]\nviews = 88449\nshares = 4733\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 204
}
|
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntitle: Progressive motivating Local Area Network\npaper_id: arXiv:2020.75228\nfunding_source: null\ncitations: 308\nabstract: Economic prepare already here account read society. Professor start family\n mouth out.\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 131
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output news article as JSON."
},
{
"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-8885825\",\n \"headline\": \"Function-based secondary workforce\",\n \"author\": \"Rebecca Harris\",\n \"published\": \"2026-01-04T06:26:20.552142\",\n \"section\": \"Politics\",\n \"content\": \"Determine event eight figure worker must. Of war learn identify national process hard administration.\\nNow compare idea herself simple. Such article the traditional.\\nClearly culture win political green. Allow forget budget. Old not include program authority.\",\n \"tags\": [\n \"determine\",\n \"suffer\",\n \"image\"\n ],\n \"views\": 26326,\n \"shares\": 4401\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 216
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate clinical note data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: 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 \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"I63\"\n }\n ],\n \"note_id\": \"CN-3421273\",\n \"vitals\": {\n \"bp\": \"91/61\",\n \"hr\": 115,\n \"temp_f\": 99.4\n }\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 125
}
|
[
{
"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 product listing."
},
{
"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-727346</product_id>\n<name>Triple-buffered contextually-based protocol</name>\n<category>electronics</category>\n<price>425.99</price>\n<currency>USD</currency>\n<stock>856</stock>\n<is_available>True</is_available>\n<rating>2.25</rating>\n<reviews>79</reviews>\n<specs>\n<weight_kg>9.08</weight_kg>\n<dimensions>84x59x50cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 184
}
|
[
{
"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-52140854\",\n \"platform\": \"facebook\",\n \"user_id\": \"c9965ea0-1db6-413c-bd65-43b7bcfcf69d\",\n \"username\": \"ksullivan\",\n \"content\": \"Heavy friend huge teacher project certainly see. Movie after spring main anyone at each fund. Industry area occur decision. Better clear degree week kid require.\",\n \"timestamp\": \"2026-01-20T00:31:34.359113\",\n \"hashtags\": [\n \"#middle\",\n \"#investment\",\n \"#letter\"\n ],\n \"engagement\": {\n \"likes\": 4902,\n \"shares\": 104,\n \"comments\": 467\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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<social_media_post>\n<post_id>POST-52140854</post_id>\n<platform>facebook</platform>\n<user_id>c9965ea0-1db6-413c-bd65-43b7bcfcf69d</user_id>\n<username>ksullivan</username>\n<content>Heavy friend huge teacher project certainly see. Movie after spring main anyone at each fund. Industry area occur decision. Better clear degree week kid require.</content>\n<timestamp>2026-01-20T00:31:34.359113</timestamp>\n<hashtags>#middle</hashtags>\n<hashtags>#investment</hashtags>\n<hashtags>#letter</hashtags>\n<engagement>\n<likes>4902</likes>\n<shares>104</shares>\n<comments>467</comments>\n</engagement>\n</social_media_post>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 240
}
|
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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 \"post_id\": \"POST-46163842\",\n \"platform\": \"instagram\",\n \"user_id\": \"8f97c8f9-cfdf-49a9-8746-3b486676e9c5\",\n \"username\": \"logan60\",\n \"content\": \"Visit detail enjoy actually six. Food administration off majority.\\nSound soon popular low national. Drive there movement identify old improve north. Until although mind cover another protect.\",\n \"timestamp\": \"2026-01-20T00:31:33.388977\",\n \"hashtags\": [\n \"#least\",\n \"#space\"\n ],\n \"engagement\": {\n \"likes\": 4694,\n \"shares\": 675,\n \"comments\": 475\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 208
}
|
[
{
"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>Spencer, Barber and Lewis</company>\n<ticker>ULBZ</ticker>\n<quarter>Q3 2022</quarter>\n<revenue>22397404</revenue>\n<expenses>5926880</expenses>\n<net_income>12035208</net_income>\n<eps>7.59</eps>\n<metrics>\n<profit_margin>22.57</profit_margin>\n<roe>6.38</roe>\n</metrics>\n</financial_report>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report 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 \"company\": \"Spencer, Barber and Lewis\",\n \"ticker\": \"ULBZ\",\n \"quarter\": \"Q3 2022\",\n \"revenue\": 22397404,\n \"expenses\": 5926880,\n \"net_income\": 12035208,\n \"eps\": 7.59,\n \"metrics\": {\n \"profit_margin\": 22.57,\n \"roe\": 6.38\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 139
}
|
[
{
"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 \"payment_method\": \"credit_card\",\n \"txn_id\": \"TXN-50691996\",\n \"subtotal\": 855.78,\n \"tax\": 31.52\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record 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<transaction_record>\n<payment_method>credit_card</payment_method>\n<txn_id>TXN-50691996</txn_id>\n<subtotal>855.78</subtotal>\n<tax>31.52</tax>\n</transaction_record>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 131
}
|
[
{
"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: 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:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-17,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 60}, {\"\"name\"\": \"\"Metform\",MRN-660634,Isaac Garner,RX-3000409\r\n2026-01-04,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 90}, {\"\"name\"\": \"\"Metformin\"\",\",MRN-317663,Mitchell Wright,RX-7988892\r\n2026-01-16,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 30}]\",MRN-553318,Linda Walker,RX-5759918\r\n2026-01-08,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Lisinopril\"\",\",MRN-742211,James Powers,RX-8451910\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "prescription",
"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 customer review as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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<customer_review>\n<review_id>REV-8110373</review_id>\n<product_id>PROD-572438</product_id>\n<user_id>66c2dedb-cd72-472a-a285-f4f1748d4b6e</user_id>\n<rating>5</rating>\n<title>Form owner budget garden.</title>\n<content>Catch nation get month son hard easy. Region school choice listen yard.\nBreak yourself make draw another. Finish miss company.</content>\n<date>2026-01-01</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>31</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 205
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output customer review as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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 \"user_id\": \"f4f8afb0-4a38-41ef-b1a5-b13147203257\",\n \"verified_purchase\": false,\n \"content\": \"Know music now drug special let above. Career democratic strong culture until. If decade world.\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 128
}
|
[
{
"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,Catch remain rise job change single. Fly certainly finish try buy between. Poor often son view capit,,2026-01-09,41,,,,PROD-687452,4,REV-1239438,,,,,Money both attorney carry.,a1299248-5060-42f3-a1be-7c0c98ac8801,True\r\nelectronics,,USD,,,True,Secured incremental collaboration,485.44,PROD-350780,2.3,,711,91x96x41cm,29.76,768,,,\r\nelectronics,,USD,,,True,Streamlined analyzing standardization,743.93,PROD-925471,1.03,,894,48x84x18cm,14.08,622,,,\r\nbooks,,USD,,,True,User-friendly reciprocal Local Area Network,174.5,PROD-950774,1.19,,709,48x64x37cm,21.19,898,,,\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 262
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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 \"platform\": \"instagram\",\n \"post_id\": \"POST-58790004\",\n \"user_id\": \"638d8800-8f03-48b1-b693-7e8a8ff4d1a1\",\n \"username\": \"fosterjason\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 114
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the data below from YAML to TOML:\nnote_id: CN-3684007\npatient:\n mrn: MRN-555222\n age: 73\n gender: F\nencounter_date: '2026-01-11'\nchief_complaint: headache\nvitals:\n bp: 178/81\n hr: 78\n temp_f: 98.0\nassessment:\n- problem: hypertension\n icd10: K11\n- problem: diabetes\n icd10: K63\n- problem: hypertension\n icd10: I88\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note from YAML to 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. Transform values to match the target format specifications.\n\nOutput:\nnote_id = \"CN-3684007\"\nencounter_date = \"2026-01-11\"\nchief_complaint = \"headache\"\n[[assessment]]\nproblem = \"hypertension\"\nicd10 = \"K11\"\n\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"K63\"\n\n[[assessment]]\nproblem = \"hypertension\"\nicd10 = \"I88\"\n\n[patient]\nmrn = \"MRN-555222\"\nage = 73\ngender = \"F\"\n\n[vitals]\nbp = \"178/81\"\nhr = 78\ntemp_f = 98.0\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 160
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics 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:\nperiod: April 2024\ntotal_revenue: 2272073\nunits_sold: 87133\nchannels:\n- name: wholesale\n revenue: 3497325\n growth: 15.29\n- name: online\n revenue: 2756989\n growth: 16.4\ntop_products:\n- sku: SKU-2251\n sales: 419208\n- sku: SKU-1192\n sales: 479777\n- sku: SKU-2217\n sales: 395220\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "sales_analytics",
"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": "Generate lab result data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id = \"LAB-4368918\"\npatient_mrn = \"MRN-625576\"\norder_date = \"2026-01-03\"\npanel = \"CBC\"\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 98.5\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 184.7\nunit = \"mg/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 128.7\nunit = \"mg/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 63.1\nunit = \"mg/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 189.1\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 158.0\nunit = \"mg/dL\"\nflag = \"low\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"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": "Reformat the data below from TOML to JSON:\ntitle = \"Multi-channeled systemic methodology 101\"\ninstructor = \"Darren Acosta\"\nterm = \"Fall 2024\"\n[[schedule]]\nweek = 1\ntopic = \"memory\"\n\n[[schedule]]\nweek = 2\ntopic = \"forward\"\n\n[[schedule]]\nweek = 3\ntopic = \"despite\"\n\n[[schedule]]\nweek = 4\ntopic = \"daughter\"\n\n[[schedule]]\nweek = 5\ntopic = \"team\"\n\n[[schedule]]\nweek = 6\ntopic = \"federal\"\n\n[[schedule]]\nweek = 7\ntopic = \"budget\"\n\n[[schedule]]\nweek = 8\ntopic = \"shake\"\n\n[[schedule]]\nweek = 9\ntopic = \"so\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from TOML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"title\": \"Multi-channeled systemic methodology 101\",\n \"instructor\": \"Darren Acosta\",\n \"term\": \"Fall 2024\",\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n },\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"memory\"\n },\n {\n \"week\": 2,\n \"topic\": \"forward\"\n },\n {\n \"week\": 3,\n \"topic\": \"despite\"\n },\n {\n \"week\": 4,\n \"topic\": \"daughter\"\n },\n {\n \"week\": 5,\n \"topic\": \"team\"\n },\n {\n \"week\": 6,\n \"topic\": \"federal\"\n },\n {\n \"week\": 7,\n \"topic\": \"budget\"\n },\n {\n \"week\": 8,\n \"topic\": \"shake\"\n },\n {\n \"week\": 9,\n \"topic\": \"so\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 253
}
|
[
{
"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: 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,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,student_id,term,title,total_score\r\n,CRS-2583,,C,,,,,60.21,,STU-916592,,,91\r\nHMH334,CRS-8321,3,,40,30,30,Joseph Williams,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"help\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"meet\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"federal\"\"}, {\"\"week\",,Fall 2024,Cloned context-sensitive groupware 101,\r\nNOD453,CRS-6955,3,,40,30,30,Nicole White,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"food\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"customer\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"new\"\"}, {\"\"week\",,Spring 2023,Persevering disintermediate focus group 101,\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 235
}
|
[
{
"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<financial_report>\n<company>Johnson, Sutton and Perez</company>\n<ticker>TVNK</ticker>\n<quarter>Q4 2021</quarter>\n<revenue>64314663</revenue>\n<expenses>45253520</expenses>\n<net_income>17650909</net_income>\n<eps>3.25</eps>\n<metrics>\n<profit_margin>22.4</profit_margin>\n<roe>10.66</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\": \"Johnson, Sutton and Perez\",\n \"ticker\": \"TVNK\",\n \"quarter\": \"Q4 2021\",\n \"revenue\": 64314663,\n \"expenses\": 45253520,\n \"net_income\": 17650909,\n \"eps\": 3.25,\n \"metrics\": {\n \"profit_margin\": 22.4,\n \"roe\": 10.66\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 139
}
|
[
{
"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: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id: EXP-149772\ntitle: Effect of address on heavy\nmethodology:\n design: observational\n sample_size: 614\n duration_days: 285\nresults:\n- metric: efficacy\n baseline: 36.52\n endpoint: 21.13\n p_value: 0.1619\n- metric: efficacy\n baseline: 42.02\n endpoint: 20.67\n p_value: 0.263\nconclusion: non-significant\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 158
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output social media post as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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 \"timestamp\": \"2026-01-20T00:31:35.383124\",\n \"post_id\": \"POST-26134356\",\n \"user_id\": \"46aa6aa6-de8c-4156-a7f7-1070b492efc8\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 112
}
|
[
{
"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: d0574216-fcaf-450a-acdd-4cbcd17fc849\ntimestamp: '2026-01-20T00:31:34.194183'\nlevel: CRITICAL\nservice: bigService\nmessage: Image a analysis technology sport.\nstack_trace:\n- at development.py:170\n- at something.py:371\n- at high.py:169\ncontext:\n user_id: fdf89a0d-cdca-4ff4-b5c4-5da73cccc05a\n request_id: 2bab1cc9-9a58-4748-ae18-dab26b3e12c7\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 164
}
|
[
{
"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: 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:\nservice = \"glassService\"\nmessage = \"National record maintain building.\"\nstack_trace = [ \"at brother.py:371\", \"at sing.py:50\",]\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 105
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: fe9952bc-b952-40a4-97f7-b20d857d8018\ntimestamp: '2026-01-20T00:31:35.501188'\nlevel: ERROR\nservice: drawService\nmessage: Fall anything book range law.\nstack_trace:\n- at change.py:137\n- at let.py:322\ncontext:\n user_id: d338d551-972c-48bb-8ffa-0e027614b760\n request_id: 91503dda-c83c-432b-96e2-b50308243985\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 155
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-592451</product_id>\n<name>Pre-emptive bandwidth-monitored task-force</name>\n<category>clothing</category>\n<price>688.75</price>\n<currency>USD</currency>\n<stock>649</stock>\n<is_available>True</is_available>\n<rating>3.28</rating>\n<reviews>442</reviews>\n<specs>\n<weight_kg>38.54</weight_kg>\n<dimensions>70x91x50cm</dimensions>\n</specs>\n</product_listing>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing 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 \"product_id\": \"PROD-592451\",\n \"name\": \"Pre-emptive bandwidth-monitored task-force\",\n \"category\": \"clothing\",\n \"price\": 688.75,\n \"currency\": \"USD\",\n \"stock\": 649,\n \"is_available\": true,\n \"rating\": 3.28,\n \"reviews\": 442,\n \"specs\": {\n \"weight_kg\": 38.54,\n \"dimensions\": \"70x91x50cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 155
}
|
[
{
"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 \"contract_id\": \"CTR-105569\",\n \"parties\": [\n {\n \"name\": \"Wagner-Garcia\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Bates LLC\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-16\",\n \"term_months\": 46,\n \"value\": 67353,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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<contract>\n<contract_id>CTR-105569</contract_id>\n<parties>\n<name>Wagner-Garcia</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Bates LLC</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-16</effective_date>\n<term_months>46</term_months>\n<value>67353</value>\n<status>active</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 165
}
|
[
{
"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 contract."
},
{
"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-527020\nparties:\n- name: Williams, Henderson and Burton\n role: party_a\n- name: Stark Ltd\n role: party_b\neffective_date: '2026-01-11'\nterm_months: 56\nvalue: 792709\nstatus: pending\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 125
}
|
[
{
"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:\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\"\": \"\"I17\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J31\"\"}, {\"\"problem\"\": \"\"diab\",chest pain,2026-01-05,CN-1867699,74,F,MRN-370789,135/105,71,97.3\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I80\"\"}]\",headache,2026-01-15,CN-7932875,31,F,MRN-844079,168/88,97,102.2\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J45\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J19\"\"}, {\"\"problem\"\": \"\"hype\",headache,2026-01-05,CN-6607678,76,M,MRN-175078,138/71,120,100.6\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note 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<clinical_note>\n<note_id>CN-1867699</note_id>\n<patient>\n<mrn>MRN-370789</mrn>\n<age>74</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-05</encounter_date>\n<chief_complaint>chest pain</chief_complaint>\n<vitals>\n<bp>135/105</bp>\n<hr>71</hr>\n<temp_f>97.3</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>I17</icd10>\n</assessment>\n<assessment>\n<problem>diabetes</problem>\n<icd10>J31</icd10>\n</assessment>\n<assessment>\n<problem>diabetes</problem>\n<icd10>K63</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 217
}
|
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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<social_media_post>\n<username>ihernandez</username>\n<engagement>\n<likes>8132</likes>\n<shares>883</shares>\n<comments>404</comments>\n</engagement>\n<platform>twitter</platform>\n<post_id>POST-71470243</post_id>\n<hashtags>#policy</hashtags>\n<hashtags>#travel</hashtags>\n<hashtags>#fill</hashtags>\n<hashtags>#military</hashtags>\n</social_media_post>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 174
}
|
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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 \"quarter\": \"Q4 2021\",\n \"eps\": 1.57,\n \"expenses\": 72667941\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 95
}
|
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment 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<experiment_result>\n<experiment_id>EXP-811005</experiment_id>\n<title>Effect of second on large</title>\n<methodology>\n<design>observational</design>\n<sample_size>664</sample_size>\n<duration_days>54</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>82.31</baseline>\n<endpoint>33.34</endpoint>\n<p_value>0.1282</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>85.78</baseline>\n<endpoint>23.52</endpoint>\n<p_value>0.4166</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>18.71</baseline>\n<endpoint>80.03</endpoint>\n<p_value>0.2453</p_value>\n</results>\n<conclusion>significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 253
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the data below from JSON to CSV:\n{\n \"post_id\": \"POST-86374488\",\n \"platform\": \"facebook\",\n \"user_id\": \"349116ea-fea2-4f51-90cf-07cbea55430e\",\n \"username\": \"marklee\",\n \"content\": \"Billion age several food finish relationship range. Agent if law result part. Including live reason condition decade.\\nTough memory military. Strategy produce lose response plant role how.\",\n \"timestamp\": \"2026-01-20T00:31:34.879913\",\n \"hashtags\": [\n \"#decade\",\n \"#everybody\",\n \"#food\",\n \"#some\"\n ],\n \"engagement\": {\n \"likes\": 2362,\n \"shares\": 41,\n \"comments\": 391\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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:\ncontent,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username\r\nBillion age several food finish relationship range. Agent if law result part. Including live reason ,391,2362,41,\"[\"\"#decade\"\", \"\"#everybody\"\", \"\"#food\"\", \"\"#some\"\"]\",facebook,POST-86374488,2026-01-20T00:31:34.879913,349116ea-fea2-4f51-90cf-07cbea55430e,marklee\r\nMay Democrat show local generation trouble. Very believe return social wide our green. Center econom,258,6862,113,\"[\"\"#business\"\", \"\"#another\"\", \"\"#good\"\", \"\"#voice\"\"]\",twitter,POST-70166159,2026-01-20T00:31:34.883740,16ef64b9-cf7d-43e4-b843-7298f70d27eb,katrina96\r\n\"Fact Mr light official forward it.\nBillion money party wrong. Training trip building however dream i\",36,868,985,\"[\"\"#live\"\", \"\"#radio\"\", \"\"#hard\"\", \"\"#question\"\"]\",instagram,POST-64667743,2026-01-20T00:31:34.884111,ee790aff-663a-4a1c-9e99-988433e421bf,rachelaguirre\r\n\"Office stuff store if ago project. Accept national that central. Wall night debate.\nGeneration summe\",270,8191,186,\"[\"\"#cultural\"\", \"\"#top\"\", \"\"#address\"\"]\",facebook,POST-14723260,2026-01-20T00:31:34.884764,8f9232be-5c2e-4d1b-b384-99ad0b797ed6,eric52\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 371
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output news article as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\ncontent = \"People blue according seek us daughter final. Resource light light police recently level. Draw environment institution west discuss bill record difference.\\nThank firm international we marriage look. Nothing phone respond.\\nNow husband interest able defense. Evidence unit per major east listen.\"\nheadline = \"Synchronized system-worthy framework\"\ntags = [ \"safe\", \"operation\", \"recently\",]\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 175
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-9395598,Lisa Larson,,,2026-01-17T11:39:18.888865,Tech,,,48468\r\nART-4186098,Michele Rhodes,\"May increase poor me according carry soldier show. Teach movement strategy charge anyone kid.\nBag ow\",Polarized background complexity,2026-01-03T08:05:11.187302,Tech,3611,\"[\"\"certain\"\", \"\"day\"\", \"\"speech\"\", \"\"region\"\"]\",67123\r\nART-6699629,Dr. Elijah Moyer,Tonight station onto standard property plan interesting rise. Myself site into mean century despite ,Re-engineered zero tolerance system engine,2026-01-04T08:16:57.251325,Politics,2530,\"[\"\"performance\"\", \"\"still\"\", \"\"but\"\"]\",13919\r\nART-4088082,Barbara Munoz,Treat assume water son establish method. Participant fine camera voice center. Today agreement defen,Proactive scalable workforce,2026-01-07T17:22:23.361762,Tech,1543,\"[\"\"act\"\", \"\"first\"\", \"\"one\"\"]\",74914\r\nART-4542261,Matthew Knapp,\"Necessary yard speak eye brother. Heavy expert choice opportunity stuff those way.\nTend per deep. Se\",Customer-focused neutral complexity,2026-01-09T02:56:22.251824,Tech,4541,\"[\"\"piece\"\", \"\"with\"\", \"\"new\"\"]\",53095\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 359
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"company\": \"Wood PLC\",\n \"ticker\": \"BVYI\",\n \"quarter\": \"Q4 2020\",\n \"revenue\": 90068624,\n \"expenses\": 2640902,\n \"net_income\": 4963183,\n \"eps\": 4.11,\n \"metrics\": {\n \"profit_margin\": 15.06,\n \"roe\": 14.73\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 133
}
|
[
{
"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\": \"Reduced well-modulated functionalities API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/popular\": {\n \"get\": {\n \"summary\": \"Maintain green hour region.\",\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: 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Reduced well-modulated functionalities API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</popular>\n<get>\n<summary>Maintain green hour region.</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<//popular>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 227
}
|
[
{
"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:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/him_get_parameters,paths_/him_get_responses_200_description,paths_/him_get_responses_400_description,paths_/him_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Multi-lateral cohesive archive API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Give name your today image.,,,,\r\nMovement building capital perhaps job manager. Tell our stuff move nation run leave heavy. Center re,\"[{\"\"name\"\": \"\"Heather Hampton\"\", \"\"affiliation\"\": \"\"Tucker-Ashley\"\", \"\"email\"\": \"\"wisedanielle@example.com\"\"}, {\",373,Dickerson-Bartlett,,,\"[\"\"study\"\", \"\"practice\"\", \"\"like\"\", \"\"marriage\"\", \"\"international\"\"]\",,arXiv:2024.80173,,,,,10.7193/RvCm,Cell,2022,Profit-focused scalable benchmark\r\n\"Military task event grow hair year do.\nSuffer enough identify difference couple become skill. Say mo\",\"[{\"\"name\"\": \"\"Richard Rice\"\", \"\"affiliation\"\": \"\"Bradford LLC\"\", \"\"email\"\": \"\"nancy09@example.com\"\"}, {\"\"name\"\": \"\"\",157,\"Wilson, Blackwell and Thompson\",,,\"[\"\"anything\"\", \"\"song\"\", \"\"toward\"\"]\",,arXiv:2023.25892,,,,,10.4278/IgKL,Science,2020,Re-engineered composite collaboration\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification 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:\nopenapi: 3.0.0\ninfo:\n title: Multi-lateral cohesive archive API\n version: 1.0.0\npaths:\n /him:\n get:\n summary: Give name your today image.\n parameters:\n - name: param0\n in: query\n type: string\n - name: param1\n in: query\n type: string\n - name: param2\n in: query\n type: string\n responses:\n '200':\n description: Success\n '400':\n description: Bad Request\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 194
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output error log as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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 \"error_id\": \"52d03157-3fa6-4e42-9128-cbffdade2acf\",\n \"context\": {\n \"user_id\": \"f2949768-f5c0-4ab6-a8f5-3ef0d3b039c7\",\n \"request_id\": \"0782b862-4e67-4eb6-80ed-30e1f190af01\"\n },\n \"stack_trace\": [\n \"at mean.py:270\",\n \"at eight.py:325\"\n ],\n \"timestamp\": \"2026-01-20T00:31:34.248566\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 152
}
|
[
{
"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: 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 = \"e2211664-8cb0-4b18-bb98-c5f3ba61be45\"\ntimestamp = \"2026-01-20T00:31:35.610055\"\nlevel = \"ERROR\"\nservice = \"sayService\"\nmessage = \"Product lose law bag arrive pressure outside.\"\nstack_trace = [ \"at bit.py:376\", \"at present.py:467\",]\n\n[context]\nuser_id = \"e4526998-b716-49f5-9787-b17ae5ef339f\"\nrequest_id = \"e241805a-ef55-44d0-b0a5-ee31acf617e5\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 161
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate lab result data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id = \"LAB-7488831\"\npatient_mrn = \"MRN-979314\"\norder_date = \"2026-01-03\"\npanel = \"CBC\"\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 123.9\nunit = \"mg/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 91.9\nunit = \"mg/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 106.5\nunit = \"g/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 78.1\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 147.3\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 136.0\nunit = \"g/dL\"\nflag = \"low\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 206
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output research paper as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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 \"paper_id\": \"arXiv:2021.38474\",\n \"title\": \"Synergized optimizing solution\",\n \"authors\": [\n {\n \"name\": \"Kristin Stein\",\n \"affiliation\": \"Mcdonald-Holden\",\n \"email\": \"christine14@example.com\"\n },\n {\n \"name\": \"Jeffrey Richards\",\n \"affiliation\": \"Owens and Sons\",\n \"email\": \"ijones@example.org\"\n }\n ],\n \"abstract\": \"Explain reduce believe show. Wrong through station explain run.\",\n \"keywords\": [\n \"north\",\n \"American\",\n \"team\",\n \"ability\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2022,\n \"doi\": \"10.6121/ozCS\"\n },\n \"citations\": 228,\n \"funding_source\": \"Byrd-Davis\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 239
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this TOML data into YAML format:\nassessment_id = \"ASMT-591303\"\nstudent_id = \"STU-183312\"\ncourse_id = \"CRS-5596\"\ntype = \"exam\"\ndate = \"2026-01-14\"\ntotal_score = 99\npercentage = 98.03\ngrade = \"B\"\n[[scores]]\nquestion = 1\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 7\npoints_possible = 10\n\n[[scores]]\nquestion = 11\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 12\npoints_earned = 7\npoints_possible = 10\n\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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:\nassessment_id: ASMT-591303\nstudent_id: STU-183312\ncourse_id: CRS-5596\ntype: exam\ndate: '2026-01-14'\nscores:\n- question: 1\n points_earned: 10\n points_possible: 10\n- question: 2\n points_earned: 2\n points_possible: 10\n- question: 3\n points_earned: 6\n points_possible: 10\n- question: 4\n points_earned: 6\n points_possible: 10\n- question: 5\n points_earned: 1\n points_possible: 10\n- question: 6\n points_earned: 2\n points_possible: 10\n- question: 7\n points_earned: 10\n points_possible: 10\n- question: 8\n points_earned: 9\n points_possible: 10\n- question: 9\n points_earned: 3\n points_possible: 10\n- question: 10\n points_earned: 7\n points_possible: 10\n- question: 11\n points_earned: 3\n points_possible: 10\n- question: 12\n points_earned: 7\n points_possible: 10\ntotal_score: 99\npercentage: 98.03\ngrade: B\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "student_assessment",
"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": "Reformat the data below from JSON to XML:\n{\n \"result_id\": \"LAB-8855694\",\n \"patient_mrn\": \"MRN-148752\",\n \"order_date\": \"2026-01-07\",\n \"panel\": \"Lipid\",\n \"results\": [\n {\n \"test\": \"Hemoglobin\",\n \"value\": 60.5,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 152.2,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 181.7,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 59.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 146.5,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<result_id>LAB-8855694</result_id>\n<patient_mrn>MRN-148752</patient_mrn>\n<order_date>2026-01-07</order_date>\n<panel>Lipid</panel>\n<results>\n<test>Hemoglobin</test>\n<value>60.5</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>152.2</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>181.7</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>59.4</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>146.5</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n</lab_result>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "conversion",
"estimated_tokens": 252
}
|
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\nReligious forward deep Republican letter. Hear so peace. Company but PM less ten our sea.,,,None,\"[\"\"financial\"\", \"\"human\"\", \"\"choice\"\", \"\"necessary\"\"]\",,10.4334/AVan,Science,2020,Adaptive asynchronous analyzer\r\n\"Try money amount. Land have buy. Particular imagine performance charge good room.\nHis high law off. \",\"[{\"\"name\"\": \"\"Natasha Duarte\"\", \"\"affiliation\"\": \"\"Pena-Foster\"\", \"\"email\"\": \"\"keith40@example.org\"\"}, {\"\"name\"\": \",357,Carter LLC,\"[\"\"here\"\", \"\"newspaper\"\", \"\"single\"\"]\",arXiv:2020.75338,10.8064/iJZu,Cell,2022,Innovative bifurcated moratorium\r\nNice out explain. Sport market financial fish value need technology several.,\"[{\"\"name\"\": \"\"Ann Savage\"\", \"\"affiliation\"\": \"\"Little Inc\"\", \"\"email\"\": \"\"brandon45@example.com\"\"}, {\"\"name\"\": \"\"Ch\",132,None,\"[\"\"popular\"\", \"\"now\"\", \"\"wall\"\"]\",arXiv:2022.70935,10.8363/gOVE,Nature,2021,Centralized full-range analyzer\r\n\"Father accept better per happen crime ready write. Lose themselves often heavy growth financial.\nTou\",\"[{\"\"name\"\": \"\"John Garcia\"\", \"\"affiliation\"\": \"\"Wiley-Lewis\"\", \"\"email\"\": \"\"carlosolson@example.com\"\"}, {\"\"name\"\":\",173,\"Williams, Brown and Morrison\",\"[\"\"oil\"\", \"\"why\"\", \"\"north\"\", \"\"society\"\"]\",arXiv:2022.18012,10.8210/PiZa,Cell,2020,Function-based interactive product\r\nFind no wide catch consumer section sea. Per under win dark when affect relationship pattern. Health,\"[{\"\"name\"\": \"\"Donna Wells\"\", \"\"affiliation\"\": \"\"Chaney, Griffith and Davis\"\", \"\"email\"\": \"\"anthonyconley@exampl\",469,None,\"[\"\"eight\"\", \"\"ten\"\", \"\"important\"\", \"\"science\"\"]\",arXiv:2022.71169,10.4793/VYMq,Nature,2020,Face-to-face coherent forecast\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 507
}
|
[
{
"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 \"experiment_id\": \"EXP-838577\",\n \"title\": \"Effect of without on network\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 635,\n \"duration_days\": 365\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 81.98,\n \"endpoint\": 23.58,\n \"p_value\": 0.0713\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 96.36,\n \"endpoint\": 22.98,\n \"p_value\": 0.4679\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 68.65,\n \"endpoint\": 13.26,\n \"p_value\": 0.1655\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-838577</experiment_id>\n<title>Effect of without on network</title>\n<methodology>\n<design>RCT</design>\n<sample_size>635</sample_size>\n<duration_days>365</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>81.98</baseline>\n<endpoint>23.58</endpoint>\n<p_value>0.0713</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>96.36</baseline>\n<endpoint>22.98</endpoint>\n<p_value>0.4679</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>68.65</baseline>\n<endpoint>13.26</endpoint>\n<p_value>0.1655</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 254
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following JSON to TOML:\n{\n \"txn_id\": \"TXN-33897504\",\n \"customer_id\": \"e0c406b1-092b-45c3-881d-1c7171fa97c2\",\n \"timestamp\": \"2026-01-20T00:31:33.993242\",\n \"items\": [\n {\n \"sku\": \"SKU-22636\",\n \"qty\": 1,\n \"price\": 366.04\n },\n {\n \"sku\": \"SKU-85344\",\n \"qty\": 4,\n \"price\": 19.71\n },\n {\n \"sku\": \"SKU-95064\",\n \"qty\": 2,\n \"price\": 154.93\n }\n ],\n \"subtotal\": 1067.96,\n \"tax\": 61.95,\n \"total\": 681.85,\n \"payment_method\": \"paypal\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record from JSON to 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. Transform values to match the target format specifications.\n\nOutput:\ntxn_id = \"TXN-33897504\"\ncustomer_id = \"e0c406b1-092b-45c3-881d-1c7171fa97c2\"\ntimestamp = \"2026-01-20T00:31:33.993242\"\nsubtotal = 1067.96\ntax = 61.95\ntotal = 681.85\npayment_method = \"paypal\"\n[[items]]\nsku = \"SKU-22636\"\nqty = 1\nprice = 366.04\n\n[[items]]\nsku = \"SKU-85344\"\nqty = 4\nprice = 19.71\n\n[[items]]\nsku = \"SKU-95064\"\nqty = 2\nprice = 154.93\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 162
}
|
[
{
"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<transaction_record>\n<items>\n<sku>SKU-61835</sku>\n<qty>3</qty>\n<price>51.27</price>\n</items>\n<items>\n<sku>SKU-60648</sku>\n<qty>3</qty>\n<price>19.11</price>\n</items>\n<items>\n<sku>SKU-17803</sku>\n<qty>4</qty>\n<price>444.56</price>\n</items>\n<items>\n<sku>SKU-96973</sku>\n<qty>5</qty>\n<price>91.38</price>\n</items>\n<timestamp>2026-01-20T00:31:33.683630</timestamp>\n<subtotal>1471.23</subtotal>\n</transaction_record>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record 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 \"items\": [\n {\n \"sku\": \"SKU-61835\",\n \"qty\": 3,\n \"price\": 51.27\n },\n {\n \"sku\": \"SKU-60648\",\n \"qty\": 3,\n \"price\": 19.11\n },\n {\n \"sku\": \"SKU-17803\",\n \"qty\": 4,\n \"price\": 444.56\n },\n {\n \"sku\": \"SKU-96973\",\n \"qty\": 5,\n \"price\": 91.38\n }\n ],\n \"timestamp\": \"2026-01-20T00:31:33.683630\",\n \"subtotal\": 1471.23\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 179
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nelectronics,USD,True,Upgradable 6thgeneration parallelism,13.91,PROD-110690,3.7,685,14x45x32cm,3.51,874\r\nelectronics,USD,True,Assimilated contextually-based process improvement,552.16,PROD-614231,1.46,315,13x56x51cm,6.03,860\r\nbooks,USD,True,Triple-buffered grid-enabled structure,224.12,PROD-265792,3.0,267,26x23x61cm,17.95,617\r\nelectronics,USD,True,Managed dedicated flexibility,499.03,PROD-500890,3.22,287,28x44x94cm,42.48,307\r\nbooks,USD,True,Mandatory bottom-line capability,685.15,PROD-595609,1.2,440,94x35x60cm,6.74,887\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 235
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in JSON\n2. Complexity: 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-371128\",\n \"student_id\": \"STU-973570\",\n \"course_id\": \"CRS-3343\",\n \"type\": \"quiz\",\n \"date\": \"2026-01-08\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 6,\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\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 1,\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\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 3,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 65,\n \"percentage\": 89.34,\n \"grade\": \"B\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 329
}
|
[
{
"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\": \"May 2022\",\n \"total_revenue\": 5843608,\n \"units_sold\": 47108,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 1570514,\n \"growth\": 26.59\n },\n {\n \"name\": \"online\",\n \"revenue\": 4070851,\n \"growth\": 42.79\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-7456\",\n \"sales\": 476146\n },\n {\n \"sku\": \"SKU-7096\",\n \"sales\": 237189\n },\n {\n \"sku\": \"SKU-3765\",\n \"sales\": 85559\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>May 2022</period>\n<total_revenue>5843608</total_revenue>\n<units_sold>47108</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>1570514</revenue>\n<growth>26.59</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>4070851</revenue>\n<growth>42.79</growth>\n</channels>\n<top_products>\n<sku>SKU-7456</sku>\n<sales>476146</sales>\n</top_products>\n<top_products>\n<sku>SKU-7096</sku>\n<sales>237189</sales>\n</top_products>\n<top_products>\n<sku>SKU-3765</sku>\n<sales>85559</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": "Produce a JSON document for a news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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 \"article_id\": \"ART-5766974\",\n \"headline\": \"Decentralized maximized challenge\",\n \"author\": \"Dr. Eric Miller MD\",\n \"published\": \"2026-01-04T16:46:57.191248\",\n \"section\": \"Business\",\n \"content\": \"Western experience subject current contain whether. Sell college camera amount none. Outside experience somebody.\\nRead challenge go degree almost. Place number language positive serve part high.\",\n \"tags\": [\n \"wall\",\n \"reality\",\n \"while\",\n \"company\",\n \"every\"\n ],\n \"views\": 66879,\n \"shares\": 3461\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 207
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate transaction record data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in JSON\n2. Complexity: 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 \"txn_id\": \"TXN-61338952\",\n \"customer_id\": \"576aca2d-b4d5-4a49-aba1-d07e4b995289\",\n \"timestamp\": \"2026-01-20T00:31:34.638128\",\n \"items\": [\n {\n \"sku\": \"SKU-72393\",\n \"qty\": 5,\n \"price\": 38.58\n }\n ],\n \"subtotal\": 1635.22,\n \"tax\": 28.13,\n \"total\": 2050.31,\n \"payment_method\": \"credit_card\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 158
}
|
[
{
"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 contract."
},
{
"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-169518\nparties:\n- name: Robinson-Holmes\n role: party_a\n- name: Barker, Morgan and Griffith\n role: party_b\neffective_date: '2026-01-10'\nterm_months: 40\nvalue: 683910\nstatus: pending\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 126
}
|
[
{
"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<social_media_post>\n<post_id>POST-79841095</post_id>\n<platform>twitter</platform>\n<user_id>bfb2d100-e0ce-4072-8da6-7f392d1a23fa</user_id>\n<username>richard12</username>\n<content>Represent also purpose cut sort paper. Own tell officer including.\nIts data worker. Alone part the person material teacher. Control purpose test lose two.</content>\n<timestamp>2026-01-20T00:31:35.098521</timestamp>\n<hashtags>#approach</hashtags>\n<hashtags>#hotel</hashtags>\n<hashtags>#increase</hashtags>\n<engagement>\n<likes>864</likes>\n<shares>968</shares>\n<comments>135</comments>\n</engagement>\n</social_media_post>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post 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 \"post_id\": \"POST-79841095\",\n \"platform\": \"twitter\",\n \"user_id\": \"bfb2d100-e0ce-4072-8da6-7f392d1a23fa\",\n \"username\": \"richard12\",\n \"content\": \"Represent also purpose cut sort paper. Own tell officer including.\\nIts data worker. Alone part the person material teacher. Control purpose test lose two.\",\n \"timestamp\": \"2026-01-20T00:31:35.098521\",\n \"hashtags\": [\n \"#approach\",\n \"#hotel\",\n \"#increase\"\n ],\n \"engagement\": {\n \"likes\": 864,\n \"shares\": 968,\n \"comments\": 135\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 205
}
|
End of preview. Expand
in Data Studio
structured_data_with_cot_dataset
このデータセットは、様々な形式（JSON、XML、YAML、TOML、CSV）の構造化データと、それぞれに対応する簡潔な思考連鎖（Chain-of-Thought, CoT）推論を含む多様な例を提供します。
データセットの概要
- messages: OpenAIチャット形式 (system, user, assistant)
- metadata: format, complexity, schema, estimated_tokens
サポートされるデータ形式
- JSON, XML, YAML, TOML, CSV
生成方法
Fakerライブラリを使用し、Pythonスクリプトで生成。検証用・テスト用に分割済み。
- Downloads last month
- 39
Size of downloaded dataset files:
7.49 MB
Size of the auto-converted Parquet files:
2.05 MB
Number of rows:
5,050