messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output course syllabus as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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<course_syllabus>\n<course_id>CRS-5723</course_id>\n<code>RDP371</code>\n<title>Synergistic exuding implementation 101</title>\n<instructor>Tammy Cowan</instructor>\n<credits>3</credits>\n<term>Spring 2024</term>\n<schedule>\n<week>1</week>\n<topic>safe</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>impact</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>guy</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>national</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>exactly</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>American</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>send</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>indeed</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"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": "Generate financial report data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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<financial_report>\n<company>Wright Inc</company>\n<ticker>IJTW</ticker>\n<quarter>Q3 2023</quarter>\n<revenue>39372998</revenue>\n<expenses>18936415</expenses>\n<net_income>13383540</net_income>\n<eps>3.85</eps>\n<metrics>\n<profit_margin>13.41</profit_margin>\n<roe>24.47</roe>\n</metrics>\n</financial_report>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate social media post data in XML format."
},
{
"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>william38</username>\n<timestamp>2026-01-07T01:26:12.042358</timestamp>\n<hashtags>#involve</hashtags>\n<hashtags>#bag</hashtags>\n<hashtags>#military</hashtags>\n<post_id>POST-66097562</post_id>\n<user_id>816ca948-4ab6-4225-8820-fe024a0cab43</user_id>\n</social_media_post>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 163
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<helpful_votes>92</helpful_votes>\n<content>Tv full before card list of believe. Produce street education run. Close force forward power think responsibility.</content>\n<user_id>d5eaa5d8-0812-4bf0-9a07-a852219611d8</user_id>\n</customer_review>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 153
} |
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Montes-Richardson\nticker: NZLE\nquarter: Q4 2021\nrevenue: 27172554\nexpenses: 16565013\nnet_income: 15418036\neps: 2.53\nmetrics:\n profit_margin: 6.13\n roe: 10.3\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 120
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output transaction record as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in CSV\n2. Complexity: 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:\ncustomer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id\r\ndcc085d4-ca03-463a-a9b5-157b38cd0e07,\"[{\"\"sku\"\": \"\"SKU-85146\"\", \"\"qty\"\": 2, \"\"price\"\": 497.36}, {\"\"sku\"\": \"\"SKU-77940\"\", \"\"qty\"\": 1, \"\"price\"\": 153.37}, {\",paypal,1921.97,84.11,2026-01-07T01:26:12.612650,783.92,TXN-46065837\r\nea44414f-147d-451e-86b4-f80b74290b58,\"[{\"\"sku\"\": \"\"SKU-57984\"\", \"\"qty\"\": 4, \"\"price\"\": 362.21}, {\"\"sku\"\": \"\"SKU-20621\"\", \"\"qty\"\": 1, \"\"price\"\": 119.04}]\",apple_pay,1346.15,116.61,2026-01-07T01:26:12.616158,1506.89,TXN-85807998\r\n6f90192d-064e-46d1-be4b-9766fce84834,\"[{\"\"sku\"\": \"\"SKU-42350\"\", \"\"qty\"\": 2, \"\"price\"\": 77.42}]\",credit_card,1442.24,7.3,2026-01-07T01:26:12.616207,943.57,TXN-32164943\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "transaction_record",
"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": "Generate api specification data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Realigned methodical project API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</they>\n<get>\n<summary>Work value those range.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param2</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//they>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 236
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following YAML to JSON:\nmethodology:\n design: observational\n sample_size: 113\n duration_days: 190\nconclusion: non-significant\ntitle: Effect of mean on gun\nexperiment_id: EXP-949926\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from YAML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"methodology\": {\n \"design\": \"observational\",\n \"sample_size\": 113,\n \"duration_days\": 190\n },\n \"conclusion\": \"non-significant\",\n \"title\": \"Effect of mean on gun\",\n \"experiment_id\": \"EXP-949926\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 133
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-638404</contract_id>\n<parties>\n<name>Nguyen-Morrison</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Higgins-Brewer</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-02</effective_date>\n<term_months>16</term_months>\n<value>256101</value>\n<status>active</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ncontract_id: CTR-638404\nparties:\n- name: Nguyen-Morrison\n role: party_a\n- name: Higgins-Brewer\n role: party_b\neffective_date: '2026-01-02'\nterm_months: 16\nvalue: 256101\nstatus: active\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 124
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output contract as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-212500</contract_id>\n<effective_date>2026-01-01</effective_date>\n<status>active</status>\n<term_months>12</term_months>\n</contract>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 126
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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:\nexperiment_id = \"EXP-886870\"\ntitle = \"Effect of help on one\"\nconclusion = \"non-significant\"\n[[results]]\nmetric = \"efficacy\"\nbaseline = 90.99\nendpoint = 14.12\np_value = 0.2399\n\n[[results]]\nmetric = \"safety\"\nbaseline = 49.62\nendpoint = 41.31\np_value = 0.1533\n\n[methodology]\ndesign = \"observational\"\nsample_size = 967\nduration_days = 208\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output financial report as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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:\ncompany = \"Martinez, Johns and Dawson\"\nticker = \"MCLW\"\nquarter = \"Q3 2023\"\nrevenue = 8871585\nexpenses = 63481985\nnet_income = 12818637\neps = 0.92\n\n[metrics]\nprofit_margin = 23.47\nroe = 24.67\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 122
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate transaction record data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncustomer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id\r\n2f7988da-c001-4d4e-850c-f99986363268,\"[{\"\"sku\"\": \"\"SKU-52213\"\", \"\"qty\"\": 5, \"\"price\"\": 230.78}, {\"\"sku\"\": \"\"SKU-37815\"\", \"\"qty\"\": 4, \"\"price\"\": 27.45}]\",apple_pay,1760.58,139.95,2026-01-07T01:26:15.010643,806.5,TXN-34939831\r\n3f4414ee-4732-453f-a77f-d9c859067c97,\"[{\"\"sku\"\": \"\"SKU-48538\"\", \"\"qty\"\": 1, \"\"price\"\": 75.52}, {\"\"sku\"\": \"\"SKU-39092\"\", \"\"qty\"\": 1, \"\"price\"\": 233.82}, {\"\"\",credit_card,888.67,15.21,2026-01-07T01:26:15.011709,80.1,TXN-42022904\r\n8a9d0918-d86d-43e0-bff1-1a912f85470a,\"[{\"\"sku\"\": \"\"SKU-34509\"\", \"\"qty\"\": 4, \"\"price\"\": 21.17}]\",paypal,1015.02,5.63,2026-01-07T01:26:15.011771,1883.23,TXN-47943285\r\na517a68b-8973-4a6d-8464-79fe15ebc55c,\"[{\"\"sku\"\": \"\"SKU-80651\"\", \"\"qty\"\": 3, \"\"price\"\": 497.64}, {\"\"sku\"\": \"\"SKU-11730\"\", \"\"qty\"\": 1, \"\"price\"\": 338.41}, {\",credit_card,950.7,56.81,2026-01-07T01:26:15.011831,670.45,TXN-80034383\r\n230a6da1-68ff-4825-b374-6f998c39fb1b,\"[{\"\"sku\"\": \"\"SKU-69240\"\", \"\"qty\"\": 2, \"\"price\"\": 316.15}, {\"\"sku\"\": \"\"SKU-27350\"\", \"\"qty\"\": 5, \"\"price\"\": 98.86}, {\"\"\",apple_pay,416.01,93.63,2026-01-07T01:26:15.011884,181.72,TXN-74096038\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 364
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate experiment result data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment 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:\nexperiment_id = \"EXP-565695\"\ntitle = \"Effect of toward on stop\"\nconclusion = \"non-significant\"\n[[results]]\nmetric = \"efficacy\"\nbaseline = 72.19\nendpoint = 65.67\np_value = 0.4453\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 42.8\nendpoint = 19.76\np_value = 0.4179\n\n[[results]]\nmetric = \"safety\"\nbaseline = 32.32\nendpoint = 41.26\np_value = 0.0031\n\n[methodology]\ndesign = \"cohort\"\nsample_size = 107\nduration_days = 350\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 178
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate prescription data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-1746971\",\n \"patient_mrn\": \"MRN-694230\",\n \"prescriber\": \"Robert Gregory\",\n \"date\": \"2026-01-03\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 90\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"TID\",\n \"quantity\": 90\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 197
} |
[
{
"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 research paper."
},
{
"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:2023.96733\",\n \"title\": \"Implemented homogeneous neural-net\",\n \"authors\": [\n {\n \"name\": \"Melissa Warren\",\n \"affiliation\": \"West Inc\",\n \"email\": \"margarethill@example.org\"\n },\n {\n \"name\": \"Albert Walters\",\n \"affiliation\": \"Phillips, Johnson and Keith\",\n \"email\": \"chelsea88@example.org\"\n }\n ],\n \"abstract\": \"College leg little artist country. Result also pass share. Effect attack position speech organization long pretty.\",\n \"keywords\": [\n \"add\",\n \"like\",\n \"live\",\n \"and\"\n ],\n \"publication\": {\n \"venue\": \"Nature\",\n \"year\": 2022,\n \"doi\": \"10.9072/QlND\"\n },\n \"citations\": 77,\n \"funding_source\": null\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "generation",
"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": "Generate clinical note data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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<clinical_note>\n<note_id>CN-9050287</note_id>\n<vitals>\n<bp>163/70</bp>\n<hr>116</hr>\n<temp_f>98.5</temp_f>\n</vitals>\n<chief_complaint>chest pain</chief_complaint>\n<encounter_date>2026-01-05</encounter_date>\n</clinical_note>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 143
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output lab result as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"result_id\": \"LAB-9642328\",\n \"patient_mrn\": \"MRN-347729\",\n \"order_date\": \"2026-01-06\",\n \"panel\": \"CBC\",\n \"results\": [\n {\n \"test\": \"Hemoglobin\",\n \"value\": 177.1,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 64.2,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 131.0,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 58.1,\n \"unit\": \"g/dL\",\n \"flag\": \"normal\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 214
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate api specification data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/house_get_parameters,paths_/house_get_responses_200_description,paths_/house_get_responses_400_description,paths_/house_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Self-enabling neutral utilization API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}]\",Success,Bad Request,Recent painting response effort special own ever e,,,,\r\nDark stage attention. Camera talk should study after condition future. Chance clearly gun prove imag,\"[{\"\"name\"\": \"\"Jason Wright\"\", \"\"affiliation\"\": \"\"Steele Inc\"\", \"\"email\"\": \"\"chanwilliam@example.com\"\"}, {\"\"name\"\":\",433,Ortiz Inc,,,\"[\"\"and\"\", \"\"detail\"\", \"\"side\"\", \"\"feeling\"\", \"\"little\"\"]\",,arXiv:2024.48127,,,,,10.7296/xYWs,Cell,2022,Focused bifurcated policy\r\n\"Day artist establish.\nForeign you budget training. Agree than guess soldier. Cultural time sense tho\",\"[{\"\"name\"\": \"\"Phillip Mclean\"\", \"\"affiliation\"\": \"\"Walker, Merritt and Woods\"\", \"\"email\"\": \"\"debra01@example.co\",4,Carr Inc,,,\"[\"\"in\"\", \"\"sound\"\", \"\"environmental\"\", \"\"family\"\"]\",,arXiv:2021.83535,,,,,10.1968/kaqO,Cell,2024,Future-proofed 3rdgeneration groupware\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 383
} |
[
{
"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: 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 \"content\": \"Type participant summer successful. Statement marriage wonder skin plant. Wall institution explain different low.\\nRecently senior usually military tonight sit. Put necessary just notice exist movie. Raise investment loss effort oil.\",\n \"author\": \"Amanda Jennings\",\n \"headline\": \"Streamlined 24hour orchestration\",\n \"section\": \"Politics\",\n \"views\": 37603\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 172
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"experiment_id\": \"EXP-826350\",\n \"title\": \"Effect of decision on who\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 605,\n \"duration_days\": 103\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 56.04,\n \"endpoint\": 39.98,\n \"p_value\": 0.2349\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 79.65,\n \"endpoint\": 52.3,\n \"p_value\": 0.0188\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 191
} |
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Hunt, Byrd and Taylor\nticker: WJGR\nquarter: Q3 2020\nrevenue: 9059648\nexpenses: 70825887\nnet_income: 7626987\neps: 2.68\nmetrics:\n profit_margin: 6.55\n roe: 5.91\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 121
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"title\": \"Effect of because on hand\",\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 99.92,\n \"endpoint\": 31.19,\n \"p_value\": 0.3637\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 79.88,\n \"endpoint\": 40.14,\n \"p_value\": 0.4331\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 57.72,\n \"endpoint\": 41.74,\n \"p_value\": 0.1666\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 47.88,\n \"endpoint\": 85.33,\n \"p_value\": 0.3608\n }\n ],\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 765,\n \"duration_days\": 241\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result 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<experiment_result>\n<title>Effect of because on hand</title>\n<results>\n<metric>efficacy</metric>\n<baseline>99.92</baseline>\n<endpoint>31.19</endpoint>\n<p_value>0.3637</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>79.88</baseline>\n<endpoint>40.14</endpoint>\n<p_value>0.4331</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>57.72</baseline>\n<endpoint>41.74</endpoint>\n<p_value>0.1666</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>47.88</baseline>\n<endpoint>85.33</endpoint>\n<p_value>0.3608</p_value>\n</results>\n<methodology>\n<design>RCT</design>\n<sample_size>765</sample_size>\n<duration_days>241</duration_days>\n</methodology>\n</experiment_result>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 265
} |
[
{
"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 customer review."
},
{
"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-5519373</review_id>\n<product_id>PROD-172310</product_id>\n<user_id>fba9b5bd-8a47-405b-b46f-a8d8db6ec9ef</user_id>\n<rating>3</rating>\n<title>Professional if consumer quickly structure.</title>\n<content>Arrive evening event determine. Ball teacher catch view tax all guess. Box paper scene wall oil.\nGun guess pretty person apply one treat.</content>\n<date>2026-01-01</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>69</helpful_votes>\n</customer_review>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 212
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate experiment result data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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 \"title\": \"Effect of call on sister\",\n \"methodology\": {\n \"design\": \"observational\",\n \"sample_size\": 443,\n \"duration_days\": 106\n },\n \"experiment_id\": \"EXP-625412\",\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 68.03,\n \"endpoint\": 10.22,\n \"p_value\": 0.4955\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 68.02,\n \"endpoint\": 12.75,\n \"p_value\": 0.4032\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 55.45,\n \"endpoint\": 30.99,\n \"p_value\": 0.0739\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 214
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<value>97981</value>\n<status>pending</status>\n<effective_date>2026-01-01</effective_date>\n<parties>\n<name>Merritt, Singh and Fitzgerald</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Weaver PLC</name>\n<role>party_b</role>\n</parties>\n<term_months>39</term_months>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"value\": 97981,\n \"status\": \"pending\",\n \"effective_date\": \"2026-01-01\",\n \"parties\": [\n {\n \"name\": \"Merritt, Singh and Fitzgerald\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Weaver PLC\",\n \"role\": \"party_b\"\n }\n ],\n \"term_months\": 39\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 145
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate sales analytics data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,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\"\": 2251154, \"\"growth\"\": -6.18}, {\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 1590431, \"\"gr\",,,,,May 2020,,,,,\"[{\"\"sku\"\": \"\"SKU-1166\"\", \"\"sales\"\": 86000}, {\"\"sku\"\": \"\"SKU-1673\"\", \"\"sales\"\": 157139}, {\"\"sku\"\": \"\"SKU-3931\"\", \"\"sal\",1534856,63135\r\nCase option training population positive. Yet pretty street personal nor best effort. Watch hope ana,\"[{\"\"name\"\": \"\"Mary Hawkins DDS\"\", \"\"affiliation\"\": \"\"Carey and Sons\"\", \"\"email\"\": \"\"allenwendy@example.com\"\"}, {\",,282,Medina and Sons,\"[\"\"owner\"\", \"\"ahead\"\", \"\"cut\"\", \"\"Mrs\"\"]\",arXiv:2024.11995,,10.9423/XzRY,Nature,2022,De-engineered secondary initiative,,,\r\nHotel before firm suddenly. Most less include remember from region picture.,\"[{\"\"name\"\": \"\"Shannon Arroyo DVM\"\", \"\"affiliation\"\": \"\"Garcia-Montes\"\", \"\"email\"\": \"\"melissa21@example.com\"\"}, {\",,476,None,\"[\"\"prevent\"\", \"\"meet\"\", \"\"since\"\"]\",arXiv:2024.71209,,10.2571/IRud,Science,2023,Exclusive incremental utilization,,,\r\nDecision act assume positive later. Entire start beautiful hit.,\"[{\"\"name\"\": \"\"Christopher Love\"\", \"\"affiliation\"\": \"\"Dominguez PLC\"\", \"\"email\"\": \"\"jtorres@example.com\"\"}, {\"\"nam\",,377,None,\"[\"\"together\"\", \"\"entire\"\", \"\"table\"\"]\",arXiv:2024.38176,,10.5160/zEGs,Cell,2021,Down-sized object-oriented strategy,,,\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 436
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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<student_assessment>\n<assessment_id>ASMT-488443</assessment_id>\n<student_id>STU-547727</student_id>\n<course_id>CRS-2527</course_id>\n<type>assignment</type>\n<date>2026-01-05</date>\n<scores>\n<question>1</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>87</total_score>\n<percentage>95.16</percentage>\n<grade>A</grade>\n</student_assessment>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 383
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following JSON to YAML:\n{\n \"paths\": {\n \"/idea\": {\n \"get\": {\n \"summary\": \"Treatment will owner couple from inside.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n },\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Multi-tiered incremental intranet API\",\n \"version\": \"1.0.0\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\npaths:\n /idea:\n get:\n summary: Treatment will owner couple from inside.\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\nopenapi: 3.0.0\ninfo:\n title: Multi-tiered incremental intranet API\n version: 1.0.0\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 200
} |
[
{
"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 product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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<product_listing>\n<product_id>PROD-690931</product_id>\n<specs>\n<weight_kg>2.83</weight_kg>\n<dimensions>20x41x26cm</dimensions>\n</specs>\n<reviews>506</reviews>\n</product_listing>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 132
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\nHe let least career sound item. Entire before some not investment.,\"[{\"\"name\"\": \"\"Debra Butler\"\", \"\"affiliation\"\": \"\"Thompson Ltd\"\", \"\"email\"\": \"\"kingjennifer@example.org\"\"}, {\"\"nam\",22,Rodriguez Inc,\"[\"\"raise\"\", \"\"everyone\"\", \"\"approach\"\", \"\"edge\"\", \"\"sort\"\"]\",arXiv:2020.58494,10.5639/VDJk,Cell,2024,Object-based uniform framework\r\nSafe lot husband customer everybody as. With all story every.,\"[{\"\"name\"\": \"\"Daniel Lopez\"\", \"\"affiliation\"\": \"\"Hernandez, Rhodes and Walker\"\", \"\"email\"\": \"\"jessicagordon@exa\",82,None,\"[\"\"report\"\", \"\"pick\"\", \"\"thank\"\", \"\"important\"\"]\",arXiv:2023.31110,10.9540/atsJ,Nature,2022,Function-based system-worthy policy\r\nKeep send bit health. Watch end product three. Government reflect reduce hold.,\"[{\"\"name\"\": \"\"Jillian Adkins\"\", \"\"affiliation\"\": \"\"Lynch, Ross and Ellis\"\", \"\"email\"\": \"\"calvarez@example.net\"\"}\",357,Carroll-Bush,\"[\"\"author\"\", \"\"floor\"\", \"\"better\"\", \"\"want\"\", \"\"month\"\"]\",arXiv:2021.65179,10.1104/kkxp,Nature,2022,Operative next generation open architecture\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 357
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"paper_id\": \"arXiv:2021.70700\",\n \"title\": \"Front-line analyzing info-mediaries\",\n \"authors\": [\n {\n \"name\": \"Mary Mason\",\n \"affiliation\": \"White-Bennett\",\n \"email\": \"bhoover@example.net\"\n },\n {\n \"name\": \"Carl Schwartz\",\n \"affiliation\": \"Cross, Castillo and Jones\",\n \"email\": \"kevin37@example.com\"\n }\n ],\n \"abstract\": \"Enter west both the. Region pick few whom chance.\\nTheory rule artist research kid manager again. Pressure someone increase deep.\",\n \"keywords\": [\n \"only\",\n \"program\",\n \"center\",\n \"call\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2020,\n \"doi\": \"10.1021/zaeR\"\n },\n \"citations\": 416,\n \"funding_source\": null\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<research_paper>\n<paper_id>arXiv:2021.70700</paper_id>\n<title>Front-line analyzing info-mediaries</title>\n<authors>\n<name>Mary Mason</name>\n<affiliation>White-Bennett</affiliation>\n<email>bhoover@example.net</email>\n</authors>\n<authors>\n<name>Carl Schwartz</name>\n<affiliation>Cross, Castillo and Jones</affiliation>\n<email>kevin37@example.com</email>\n</authors>\n<abstract>Enter west both the. Region pick few whom chance.\nTheory rule artist research kid manager again. Pressure someone increase deep.</abstract>\n<keywords>only</keywords>\n<keywords>program</keywords>\n<keywords>center</keywords>\n<keywords>call</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2020</year>\n<doi>10.1021/zaeR</doi>\n</publication>\n<citations>416</citations>\n<funding_source />\n</research_paper>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"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": "Output course syllabus as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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 \"course_id\": \"CRS-2839\",\n \"code\": \"SUS311\",\n \"title\": \"Assimilated impactful functionalities 101\",\n \"instructor\": \"Brandon Keller\",\n \"credits\": 3,\n \"term\": \"Fall 2022\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"admit\"\n },\n {\n \"week\": 2,\n \"topic\": \"else\"\n },\n {\n \"week\": 3,\n \"topic\": \"guy\"\n },\n {\n \"week\": 4,\n \"topic\": \"feel\"\n },\n {\n \"week\": 5,\n \"topic\": \"candidate\"\n },\n {\n \"week\": 6,\n \"topic\": \"arm\"\n },\n {\n \"week\": 7,\n \"topic\": \"happen\"\n },\n {\n \"week\": 8,\n \"topic\": \"education\"\n },\n {\n \"week\": 9,\n \"topic\": \"these\"\n },\n {\n \"week\": 10,\n \"topic\": \"message\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 280
} |
[
{
"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 prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription 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<prescription>\n<prescriber>Charles Mccarthy</prescriber>\n<patient_mrn>MRN-134957</patient_mrn>\n<date>2026-01-06</date>\n<rx_id>RX-2370233</rx_id>\n</prescription>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 127
} |
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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<transaction_record>\n<tax>10.01</tax>\n<total>1511.26</total>\n<subtotal>840.88</subtotal>\n<customer_id>a288eb4c-526c-44d3-aedf-80f3c4ef17e9</customer_id>\n</transaction_record>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 132
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this JSON data into YAML format:\n{\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n },\n \"term\": \"Fall 2023\",\n \"title\": \"Monitored uniform success 101\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from JSON to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ngrading:\n homework: 30\n midterm: 30\n final: 40\nterm: Fall 2023\ntitle: Monitored uniform success 101\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 106
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-6847501\npatient_mrn: MRN-637576\nprescriber: Victor Boyd\ndate: '2026-01-06'\nmedications:\n- name: Atorvastatin\n dosage: 20mg\n frequency: TID\n quantity: 30\n- name: Metformin\n dosage: 20mg\n frequency: daily\n quantity: 90\n- name: Metformin\n dosage: 5mg\n frequency: TID\n quantity: 30\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 151
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"February 2021\",\n \"total_revenue\": 5201533,\n \"units_sold\": 3107,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 1540447,\n \"growth\": 13.97\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 4981459,\n \"growth\": 40.45\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-2942\",\n \"sales\": 160144\n },\n {\n \"sku\": \"SKU-5057\",\n \"sales\": 190343\n },\n {\n \"sku\": \"SKU-5758\",\n \"sales\": 324766\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this CSV data into JSON format:\nabstract,authors,citations,content,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,timestamp,title,username\r\n,,,Pass south detail product provide. Recently board lawyer view about discuss most. Sense decision sor,,,,,,,2026-01-07T01:26:12.314571,,leematthew\r\nOnly treatment head weight across animal fly. Television nor play state commercial wish each husband,\"[{\"\"name\"\": \"\"Michael Williams\"\", \"\"affiliation\"\": \"\"Deleon, Ortiz and Harrell\"\", \"\"email\"\": \"\"pittmantyler@exa\",308,,\"Park, Moore and Roberts\",\"[\"\"back\"\", \"\"position\"\", \"\"space\"\"]\",arXiv:2024.24845,10.5912/YtFs,Nature,2021,,Phased intermediate strategy,\r\nPrevent receive join explain arrive. Rise reality drug or value south case.,\"[{\"\"name\"\": \"\"Tammy Williams\"\", \"\"affiliation\"\": \"\"Duarte, Dixon and Miller\"\", \"\"email\"\": \"\"thomas37@example.co\",148,,\"Moore, Robbins and Ortega\",\"[\"\"quality\"\", \"\"treat\"\", \"\"them\"\", \"\"manager\"\", \"\"significant\"\"]\",arXiv:2023.90295,10.1496/XLUf,Science,2020,,Ergonomic system-worthy extranet,\r\n\"Card always shoulder form. Table president hour hour challenge generation best.\nPush ask subject sen\",\"[{\"\"name\"\": \"\"Jane Jackson\"\", \"\"affiliation\"\": \"\"Perez, Hill and Livingston\"\", \"\"email\"\": \"\"rochakristin@exampl\",54,,Brown Inc,\"[\"\"month\"\", \"\"billion\"\", \"\"all\"\", \"\"by\"\"]\",arXiv:2021.70421,10.8729/nsEK,Science,2024,,Programmable context-sensitive instruction set,\r\nDefense stuff produce business writer operation. Off together weight arm.,\"[{\"\"name\"\": \"\"Jeremy Contreras\"\", \"\"affiliation\"\": \"\"Smith-Gill\"\", \"\"email\"\": \"\"snyderlaurie@example.com\"\"}, {\"\"n\",217,,None,\"[\"\"cell\"\", \"\"shake\"\", \"\"east\"\", \"\"leg\"\", \"\"lose\"\"]\",arXiv:2020.61190,10.2066/owQU,Cell,2024,,Grass-roots demand-driven frame,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from CSV to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"username\": \"leematthew\",\n \"content\": \"Pass south detail product provide. Recently board lawyer view about discuss most. Sense decision sort play.\",\n \"timestamp\": \"2026-01-07T01:26:12.314571\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 130
} |
[
{
"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 transaction record."
},
{
"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-86465796\",\n \"customer_id\": \"8f239cfc-bdbc-4a82-9121-b588096e290b\",\n \"timestamp\": \"2026-01-07T01:26:12.345353\",\n \"items\": [\n {\n \"sku\": \"SKU-78354\",\n \"qty\": 1,\n \"price\": 289.73\n },\n {\n \"sku\": \"SKU-13609\",\n \"qty\": 1,\n \"price\": 322.15\n },\n {\n \"sku\": \"SKU-34282\",\n \"qty\": 5,\n \"price\": 483.05\n }\n ],\n \"subtotal\": 706.99,\n \"tax\": 109.65,\n \"total\": 529.31,\n \"payment_method\": \"apple_pay\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 196
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate lab result data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id: LAB-9598059\npatient_mrn: MRN-375240\norder_date: '2026-01-05'\npanel: Lipid\nresults:\n- test: Hemoglobin\n value: 86.2\n unit: g/dL\n flag: high\n- test: Glucose\n value: 116.5\n unit: mg/dL\n flag: low\n- test: Glucose\n value: 131.5\n unit: mg/dL\n flag: normal\n- test: Hemoglobin\n value: 159.0\n unit: g/dL\n flag: high\n- test: Glucose\n value: 161.4\n unit: g/dL\n flag: low\n- test: Hemoglobin\n value: 87.6\n unit: mg/dL\n flag: low\n- test: WBC\n value: 102.7\n unit: g/dL\n flag: normal\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 202
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "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\nbooks,USD,True,Polarized scalable alliance,854.51,PROD-277547,4.82,690,82x98x45cm,23.67,505\r\nelectronics,USD,True,Balanced zero-defect array,413.02,PROD-772711,3.12,352,67x75x43cm,6.29,904\r\nelectronics,USD,True,Digitized tertiary productivity,323.85,PROD-953018,1.35,302,58x93x59cm,42.62,599\r\nclothing,USD,True,Ameliorated grid-enabled installation,253.12,PROD-782796,4.89,879,62x79x85cm,43.48,857\r\nclothing,USD,True,Expanded intermediate solution,585.01,PROD-453461,3.34,318,85x66x10cm,29.26,257\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"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": "Create a YAML representation of course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncourse_id: CRS-4188\ncode: QTY141\ntitle: Sharable high-level complexity 101\ninstructor: Jenny Lucas\ncredits: 3\nterm: Spring 2020\nschedule:\n- week: 1\n topic: base\n- week: 2\n topic: car\n- week: 3\n topic: star\n- week: 4\n topic: me\n- week: 5\n topic: because\n- week: 6\n topic: particular\n- week: 7\n topic: window\n- week: 8\n topic: memory\n- week: 9\n topic: rise\n- week: 10\n topic: manager\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 188
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate contract data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id = \"CTR-570925\"\neffective_date = \"2026-01-05\"\nterm_months = 50\nvalue = 698924\nstatus = \"executed\"\n[[parties]]\nname = \"Herring, Wolf and White\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Rodriguez, Lawrence and Smith\"\nrole = \"party_b\"\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 132
} |
[
{
"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 \"experiment_id\": \"EXP-235027\",\n \"title\": \"Effect of personal on mouth\",\n \"conclusion\": \"significant\",\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 65.08,\n \"endpoint\": 79.76,\n \"p_value\": 0.2187\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 70.95,\n \"endpoint\": 63.23,\n \"p_value\": 0.0104\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 36.99,\n \"endpoint\": 80.45,\n \"p_value\": 0.1853\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 14.55,\n \"endpoint\": 99.7,\n \"p_value\": 0.2575\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result 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<experiment_result>\n<experiment_id>EXP-235027</experiment_id>\n<title>Effect of personal on mouth</title>\n<conclusion>significant</conclusion>\n<results>\n<metric>safety</metric>\n<baseline>65.08</baseline>\n<endpoint>79.76</endpoint>\n<p_value>0.2187</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>70.95</baseline>\n<endpoint>63.23</endpoint>\n<p_value>0.0104</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>36.99</baseline>\n<endpoint>80.45</endpoint>\n<p_value>0.1853</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>14.55</baseline>\n<endpoint>99.7</endpoint>\n<p_value>0.2575</p_value>\n</results>\n</experiment_result>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 256
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from YAML to JSON:\nperiod: May 2021\ntotal_revenue: 1470067\nunits_sold: 54230\nchannels:\n- name: online\n revenue: 3466774\n growth: 22.09\n- name: wholesale\n revenue: 3289592\n growth: 12.19\ntop_products:\n- sku: SKU-9258\n sales: 283967\n- sku: SKU-6675\n sales: 416959\n- sku: SKU-4799\n sales: 16903\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from YAML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"period\": \"May 2021\",\n \"total_revenue\": 1470067,\n \"units_sold\": 54230,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 3466774,\n \"growth\": 22.09\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 3289592,\n \"growth\": 12.19\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-9258\",\n \"sales\": 283967\n },\n {\n \"sku\": \"SKU-6675\",\n \"sales\": 416959\n },\n {\n \"sku\": \"SKU-4799\",\n \"sales\": 16903\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-3631259\"\npatient_mrn = \"MRN-600950\"\nprescriber = \"Joshua Allen\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"5mg\"\nfrequency = \"daily\"\nquantity = 90\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this JSON data into YAML format:\n{\n \"article_id\": \"ART-8399738\",\n \"headline\": \"Organized optimizing open architecture\",\n \"author\": \"Beth Stafford\",\n \"published\": \"2026-01-04T09:16:33.586977\",\n \"section\": \"Politics\",\n \"content\": \"Machine true push miss poor we box. Best something spend quite baby degree unit our. Number identify media stock.\\nCost yeah there while. Power type TV trip before wish discuss.\\nSpecial social law while past. Data much agree sort but law. Security subject memory organization me yourself.\",\n \"tags\": [\n \"imagine\",\n \"world\",\n \"list\",\n \"million\"\n ],\n \"views\": 15471,\n \"shares\": 3595\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from JSON to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\narticle_id: ART-8399738\nheadline: Organized optimizing open architecture\nauthor: Beth Stafford\npublished: '2026-01-04T09:16:33.586977'\nsection: Politics\ncontent: 'Machine true push miss poor we box. Best something spend quite baby degree\n unit our. Number identify media stock.\n\n Cost yeah there while. Power type TV trip before wish discuss.\n\n Special social law while past. Data much agree sort but law. Security subject memory\n organization me yourself.'\ntags:\n- imagine\n- world\n- list\n- million\nviews: 15471\nshares: 3595\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 210
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output 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-8399738\"\nheadline = \"Organized optimizing open architecture\"\nauthor = \"Beth Stafford\"\npublished = \"2026-01-04T09:16:33.586977\"\nsection = \"Politics\"\ncontent = \"Machine true push miss poor we box. Best something spend quite baby degree unit our. Number identify media stock.\\nCost yeah there while. Power type TV trip before wish discuss.\\nSpecial social law while past. Data much agree sort but law. Security subject memory organization me yourself.\"\ntags = [ \"imagine\", \"world\", \"list\", \"million\",]\nviews = 15471\nshares = 3595\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 209
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output api specification as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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,info_title,info_version,keywords,openapi,paper_id,paths_/affect_get_parameters,paths_/affect_get_responses_200_description,paths_/affect_get_responses_400_description,paths_/affect_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Multi-layered object-oriented focus group API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Church in religious talk more history voice heavy.,,,,\r\nPast catch action area exactly nothing civil. Play attention watch include.,\"[{\"\"name\"\": \"\"Pamela Moore\"\", \"\"affiliation\"\": \"\"Wu-Mora\"\", \"\"email\"\": \"\"farmerdavid@example.org\"\"}, {\"\"name\"\": \"\"I\",135,None,,,\"[\"\"house\"\", \"\"suddenly\"\", \"\"theory\"\", \"\"seat\"\", \"\"chance\"\"]\",,arXiv:2020.51038,,,,,10.8138/HmAJ,Cell,2023,Organic bandwidth-monitored pricing structure\r\nClass car bed everything. Foreign true trade go food.,\"[{\"\"name\"\": \"\"Joel Nolan\"\", \"\"affiliation\"\": \"\"Wells, Pace and Romero\"\", \"\"email\"\": \"\"rgarcia@example.net\"\"}, {\"\"\",380,Parrish-Weber,,,\"[\"\"office\"\", \"\"community\"\", \"\"yourself\"\"]\",,arXiv:2021.29858,,,,,10.9064/vrmb,Cell,2020,Sharable intangible frame\r\nEducation role degree expert include six. Method sign culture front turn large information project. ,\"[{\"\"name\"\": \"\"Matthew Davis\"\", \"\"affiliation\"\": \"\"Dalton and Sons\"\", \"\"email\"\": \"\"gholmes@example.net\"\"}, {\"\"name\",499,None,,,\"[\"\"those\"\", \"\"wife\"\", \"\"project\"\", \"\"tough\"\", \"\"international\"\"]\",,arXiv:2024.17198,,,,,10.5762/kEUf,Science,2024,Reactive system-worthy Internet solution\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 481
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following YAML to JSON:\ncontract_id: CTR-598561\nparties:\n- name: Velazquez-Duran\n role: party_a\n- name: Brown Inc\n role: party_b\neffective_date: '2026-01-04'\nterm_months: 55\nvalue: 130864\nstatus: active\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from YAML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"contract_id\": \"CTR-598561\",\n \"parties\": [\n {\n \"name\": \"Velazquez-Duran\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Brown Inc\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-04\",\n \"term_months\": 55,\n \"value\": 130864,\n \"status\": \"active\"\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 148
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<research_paper>\n<keywords>however</keywords>\n<keywords>fact</keywords>\n<keywords>draw</keywords>\n<authors>\n<name>Victoria Watson</name>\n<affiliation>Key, Richards and Gomez</affiliation>\n<email>jorge18@example.net</email>\n</authors>\n<authors>\n<name>Jeremy Walker</name>\n<affiliation>Snow Group</affiliation>\n<email>laurenrodriguez@example.org</email>\n</authors>\n<authors>\n<name>Mary Boyd</name>\n<affiliation>Roberts Inc</affiliation>\n<email>courtney32@example.com</email>\n</authors>\n<paper_id>arXiv:2024.79917</paper_id>\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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 \"keywords\": [\n \"however\",\n \"fact\",\n \"draw\"\n ],\n \"authors\": [\n {\n \"name\": \"Victoria Watson\",\n \"affiliation\": \"Key, Richards and Gomez\",\n \"email\": \"jorge18@example.net\"\n },\n {\n \"name\": \"Jeremy Walker\",\n \"affiliation\": \"Snow Group\",\n \"email\": \"laurenrodriguez@example.org\"\n },\n {\n \"name\": \"Mary Boyd\",\n \"affiliation\": \"Roberts Inc\",\n \"email\": \"courtney32@example.com\"\n }\n ],\n \"paper_id\": \"arXiv:2024.79917\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 201
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output sales analytics as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold\r\n,,\"[{\"\"name\"\": \"\"wholesale\"\", \"\"revenue\"\": 1100052, \"\"growth\"\": -3.92}, {\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 1652141, \",,,,,May 2021,,,,,\"[{\"\"sku\"\": \"\"SKU-4912\"\", \"\"sales\"\": 74292}, {\"\"sku\"\": \"\"SKU-1590\"\", \"\"sales\"\": 50210}, {\"\"sku\"\": \"\"SKU-8419\"\", \"\"sale\",5805544,31472\r\nArm father stage here ten. Home safe miss successful run seat.,\"[{\"\"name\"\": \"\"Virginia Rowe\"\", \"\"affiliation\"\": \"\"Morris-Gonzalez\"\", \"\"email\"\": \"\"brandon17@example.net\"\"}, {\"\"na\",,158,Bell-Smith,\"[\"\"stand\"\", \"\"inside\"\", \"\"value\"\"]\",arXiv:2021.74732,,10.5122/cvdx,Cell,2024,Managed background encoding,,,\r\nWorker outside determine man. Entire only heavy wonder sing road. Seem kitchen play try source visit,\"[{\"\"name\"\": \"\"Katherine Hancock\"\", \"\"affiliation\"\": \"\"Frederick-James\"\", \"\"email\"\": \"\"bmitchell@example.org\"\"}, \",,310,Huynh-Singh,\"[\"\"hotel\"\", \"\"common\"\", \"\"need\"\", \"\"show\"\"]\",arXiv:2023.96460,,10.7908/FmJg,Science,2023,Synergistic contextually-based approach,,,\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 355
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<grade>C</grade>\n<scores>\n<question>1</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<percentage>81.64</percentage>\n</student_assessment>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from XML to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ngrade: C\nscores:\n- question: 1\n points_earned: 3\n points_possible: 10\n- question: 2\n points_earned: 10\n points_possible: 10\n- question: 3\n points_earned: 3\n points_possible: 10\n- question: 4\n points_earned: 4\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: 9\n points_possible: 10\npercentage: 81.64\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 186
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output financial report as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\nParks and Sons,3.42,10891840,15.14,11.53,8900730,Q4 2022,54114248,VWTF\r\nNichols Ltd,5.07,58527975,5.83,16.66,6228565,Q2 2020,33651408,RNXQ\r\n\"Paul, Smith and Harvey\",2.85,3998015,25.15,18.94,17552098,Q3 2022,92841561,GUAE\r\n\"Jenkins, Hughes and Harris\",6.42,44176075,26.47,18.85,13673740,Q3 2023,90299955,RENW\r\n\"Thompson, Berry and Martinez\",3.72,11558333,16.72,11.75,792762,Q3 2023,41281798,FHJA\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 198
} |
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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:\npost_id: POST-68027448\nplatform: instagram\nuser_id: 1798e880-1987-4210-83d6-a3c125c46cbe\nusername: okelly\ncontent: Our tough teach camera help. Yard we likely he expect question. Capital commercial\n best soon accept.\ntimestamp: '2026-01-07T01:26:14.180495'\nhashtags:\n- '#pay'\n- '#kind'\nengagement:\n likes: 3412\n shares: 593\n comments: 324\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 164
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from YAML to JSON:\ncompany: Martinez, Johns and Dawson\nticker: MCLW\nquarter: Q3 2023\nrevenue: 8871585\nexpenses: 63481985\nnet_income: 12818637\neps: 0.92\nmetrics:\n profit_margin: 23.47\n roe: 24.67\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from YAML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"company\": \"Martinez, Johns and Dawson\",\n \"ticker\": \"MCLW\",\n \"quarter\": \"Q3 2023\",\n \"revenue\": 8871585,\n \"expenses\": 63481985,\n \"net_income\": 12818637,\n \"eps\": 0.92,\n \"metrics\": {\n \"profit_margin\": 23.47,\n \"roe\": 24.67\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 139
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"assessment_id\": \"ASMT-949804\",\n \"student_id\": \"STU-999892\",\n \"course_id\": \"CRS-8579\",\n \"type\": \"quiz\",\n \"date\": \"2026-01-05\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 4,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 54,\n \"percentage\": 96.35,\n \"grade\": \"B\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 352
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in TOML\n2. Complexity: 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:\ntxn_id = \"TXN-41173343\"\ncustomer_id = \"bffcc9bf-c7ad-482d-a457-f67eac39f00a\"\ntimestamp = \"2026-01-07T01:26:14.110632\"\nsubtotal = 714.81\ntax = 120.56\ntotal = 651.41\npayment_method = \"paypal\"\n[[items]]\nsku = \"SKU-87844\"\nqty = 3\nprice = 436.0\n\n[[items]]\nsku = \"SKU-90224\"\nqty = 1\nprice = 473.23\n\n[[items]]\nsku = \"SKU-20215\"\nqty = 3\nprice = 394.67\n\n[[items]]\nsku = \"SKU-92206\"\nqty = 2\nprice = 436.8\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "transaction_record",
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"course_id\": \"CRS-1590\",\n \"code\": \"MZD331\",\n \"title\": \"User-friendly dedicated toolset 101\",\n \"instructor\": \"Jennifer Armstrong\",\n \"credits\": 3,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"nor\"\n },\n {\n \"week\": 2,\n \"topic\": \"instead\"\n },\n {\n \"week\": 3,\n \"topic\": \"improve\"\n },\n {\n \"week\": 4,\n \"topic\": \"option\"\n },\n {\n \"week\": 5,\n \"topic\": \"middle\"\n },\n {\n \"week\": 6,\n \"topic\": \"we\"\n },\n {\n \"week\": 7,\n \"topic\": \"member\"\n },\n {\n \"week\": 8,\n \"topic\": \"follow\"\n },\n {\n \"week\": 9,\n \"topic\": \"more\"\n },\n {\n \"week\": 10,\n \"topic\": \"rate\"\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": 278
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to YAML:\n{\n \"net_income\": 1392290,\n \"ticker\": \"NEEN\",\n \"quarter\": \"Q2 2023\",\n \"expenses\": 22857500,\n \"revenue\": 21273983\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from JSON to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nnet_income: 1392290\nticker: NEEN\nquarter: Q2 2023\nexpenses: 22857500\nrevenue: 21273983\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 102
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output contract as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id,effective_date,parties,status,term_months,value\r\nCTR-452178,2026-01-04,\"[{\"\"name\"\": \"\"Barton, Howard and Williamson\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Johnson-Barker\"\", \"\"role\"\": \"\"p\",pending,44,362618\r\nCTR-136740,2026-01-03,\"[{\"\"name\"\": \"\"Franco-Myers\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Flores-Austin\"\", \"\"role\"\": \"\"party_b\"\"}]\",pending,51,759397\r\nCTR-152483,2026-01-03,\"[{\"\"name\"\": \"\"Stokes-Smith\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Rangel Inc\"\", \"\"role\"\": \"\"party_b\"\"}]\",executed,56,59109\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "contract",
"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": "Convert the following JSON to XML:\n{\n \"assessment_id\": \"ASMT-626485\",\n \"student_id\": \"STU-591114\",\n \"course_id\": \"CRS-4230\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-03\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 8,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 56,\n \"percentage\": 92.13,\n \"grade\": \"A\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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<student_assessment>\n<assessment_id>ASMT-626485</assessment_id>\n<student_id>STU-591114</student_id>\n<course_id>CRS-4230</course_id>\n<type>assignment</type>\n<date>2026-01-03</date>\n<scores>\n<question>1</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>56</total_score>\n<percentage>92.13</percentage>\n<grade>A</grade>\n</student_assessment>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 442
} |
[
{
"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 transaction record."
},
{
"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-56334956</txn_id>\n<customer_id>22233344-f0f2-434c-869c-d919b13dbc85</customer_id>\n<timestamp>2026-01-07T01:26:11.318292</timestamp>\n<items>\n<sku>SKU-28497</sku>\n<qty>5</qty>\n<price>124.08</price>\n</items>\n<items>\n<sku>SKU-64150</sku>\n<qty>4</qty>\n<price>49.31</price>\n</items>\n<items>\n<sku>SKU-68367</sku>\n<qty>3</qty>\n<price>96.12</price>\n</items>\n<subtotal>767.52</subtotal>\n<tax>44.4</tax>\n<total>112.37</total>\n<payment_method>credit_card</payment_method>\n</transaction_record>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 216
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output prescription as CSV."
},
{
"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-06,,MRN-134957,Charles Mccarthy,RX-2370233\r\n2026-01-03,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Atorvastatin\",MRN-989656,Richard Carlson,RX-3256086\r\n2026-01-04,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 90}, {\"\"name\"\": \"\"Lisinopril\",MRN-559826,Kevin Smith,RX-1619421\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"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": "Reformat the data below from YAML to JSON:\ncourse_id: CRS-3990\ncode: HJC253\ntitle: Total solution-oriented adapter 101\ninstructor: Ashley Patterson\ncredits: 4\nterm: Fall 2024\nschedule:\n- week: 1\n topic: doctor\n- week: 2\n topic: management\n- week: 3\n topic: hot\n- week: 4\n topic: everyone\n- week: 5\n topic: establish\n- week: 6\n topic: understand\n- week: 7\n topic: travel\n- week: 8\n topic: sense\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from YAML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"course_id\": \"CRS-3990\",\n \"code\": \"HJC253\",\n \"title\": \"Total solution-oriented adapter 101\",\n \"instructor\": \"Ashley Patterson\",\n \"credits\": 4,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"doctor\"\n },\n {\n \"week\": 2,\n \"topic\": \"management\"\n },\n {\n \"week\": 3,\n \"topic\": \"hot\"\n },\n {\n \"week\": 4,\n \"topic\": \"everyone\"\n },\n {\n \"week\": 5,\n \"topic\": \"establish\"\n },\n {\n \"week\": 6,\n \"topic\": \"understand\"\n },\n {\n \"week\": 7,\n \"topic\": \"travel\"\n },\n {\n \"week\": 8,\n \"topic\": \"sense\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 256
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in XML\n2. Complexity: 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<student_assessment>\n<assessment_id>ASMT-519678</assessment_id>\n<student_id>STU-716601</student_id>\n<course_id>CRS-4140</course_id>\n<type>quiz</type>\n<date>2026-01-05</date>\n<scores>\n<question>1</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>62</total_score>\n<percentage>76.27</percentage>\n<grade>A</grade>\n</student_assessment>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 439
} |
[
{
"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<course_syllabus>\n<course_id>CRS-1775</course_id>\n<code>SWF476</code>\n<title>Down-sized executive Graphical User Interface 101</title>\n<instructor>Erik Walters</instructor>\n<credits>4</credits>\n<term>Fall 2023</term>\n<schedule>\n<week>1</week>\n<topic>would</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>whatever</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>support</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>decade</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>beautiful</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>consumer</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>minute</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>himself</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>skin</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>seat</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from XML to JSON\n2. Complexity: 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 \"course_id\": \"CRS-1775\",\n \"code\": \"SWF476\",\n \"title\": \"Down-sized executive Graphical User Interface 101\",\n \"instructor\": \"Erik Walters\",\n \"credits\": 4,\n \"term\": \"Fall 2023\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"would\"\n },\n {\n \"week\": 2,\n \"topic\": \"whatever\"\n },\n {\n \"week\": 3,\n \"topic\": \"support\"\n },\n {\n \"week\": 4,\n \"topic\": \"decade\"\n },\n {\n \"week\": 5,\n \"topic\": \"beautiful\"\n },\n {\n \"week\": 6,\n \"topic\": \"consumer\"\n },\n {\n \"week\": 7,\n \"topic\": \"minute\"\n },\n {\n \"week\": 8,\n \"topic\": \"himself\"\n },\n {\n \"week\": 9,\n \"topic\": \"skin\"\n },\n {\n \"week\": 10,\n \"topic\": \"seat\"\n },\n {\n \"week\": 11,\n \"topic\": \"remain\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 298
} |
[
{
"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: 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<api_specification>\n<openapi>3.0.0</openapi>\n<paths>\n</professor>\n<get>\n<summary>Party these range everybody back help.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param2</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//professor>\n</paths>\n<info>\n<title>Open-architected secondary infrastructure API</title>\n<version>1.0.0</version>\n</info>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 246
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate contract data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in CSV\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id,effective_date,parties,status,term_months,value\r\nCTR-212500,2026-01-01,,active,12,\r\nCTR-291249,2026-01-06,\"[{\"\"name\"\": \"\"Jackson Group\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Li, Hale and Wright\"\", \"\"role\"\": \"\"party_b\"\"}]\",active,27,934941\r\nCTR-770240,2026-01-03,\"[{\"\"name\"\": \"\"Miller-Norris\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Pope-Gutierrez\"\", \"\"role\"\": \"\"party_b\"\"}]\",executed,36,697017\r\nCTR-145753,2026-01-06,\"[{\"\"name\"\": \"\"Morris Group\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Arnold-Reynolds\"\", \"\"role\"\": \"\"party_b\"\"}]\",active,45,439027\r\nCTR-452745,2026-01-01,\"[{\"\"name\"\": \"\"Rogers PLC\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Williams-Alexander\"\", \"\"role\"\": \"\"party_b\"\"}]\",pending,23,531679\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 254
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate error log data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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:\nabstract,authors,citations,context_request_id,context_user_id,error_id,funding_source,keywords,level,message,paper_id,publication_doi,publication_venue,publication_year,service,stack_trace,timestamp,title\r\n,,,0ee91da4-ff69-4027-abbd-858b99ba9060,393afefc-998c-4663-a671-9ca180ff7d5c,f98ed5cf-4988-47c5-bf33-ab004d77577f,,,ERROR,Century end marriage factor item others feeling.,,,,,teacherService,\"[\"\"at impact.py:301\"\", \"\"at bring.py:254\"\"]\",2026-01-07T01:26:11.158042,\r\n\"Brother effect power station. Imagine item two partner.\nModern every option third former discussion.\",\"[{\"\"name\"\": \"\"Melissa Clark\"\", \"\"affiliation\"\": \"\"Mcfarland PLC\"\", \"\"email\"\": \"\"iharmon@example.net\"\"}, {\"\"name\"\":\",434,,,,None,\"[\"\"he\"\", \"\"people\"\", \"\"suffer\"\"]\",,,arXiv:2023.76792,10.1939/CkSW,Cell,2022,,,,Public-key interactive capability\r\nFinish strategy pay ask democratic cold task evening. Model close true. Should about top.,\"[{\"\"name\"\": \"\"Mr. Brandon Palmer\"\", \"\"affiliation\"\": \"\"Myers-Lopez\"\", \"\"email\"\": \"\"brenda28@example.org\"\"}, {\"\"na\",61,,,,Golden-Bennett,\"[\"\"election\"\", \"\"effort\"\", \"\"present\"\", \"\"market\"\"]\",,,arXiv:2020.44603,10.9880/HDwa,Cell,2021,,,,Reverse-engineered empowering architecture\r\nDay measure third and use thus full like. Truth prevent technology. Although information safe.,\"[{\"\"name\"\": \"\"Terri Fischer\"\", \"\"affiliation\"\": \"\"Mcgrath, Hill and Castillo\"\", \"\"email\"\": \"\"nancyharris@exampl\",41,,,,None,\"[\"\"within\"\", \"\"surface\"\", \"\"law\"\", \"\"draw\"\", \"\"guy\"\"]\",,,arXiv:2023.62455,10.3554/KeuE,Science,2021,,,,Organic multi-state Graphical User Interface\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 465
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output clinical note as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nnote_id = \"CN-2813545\"\nencounter_date = \"2026-01-01\"\nchief_complaint = \"chest pain\"\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"K41\"\n\n[[assessment]]\nproblem = \"hypertension\"\nicd10 = \"K90\"\n\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"J65\"\n\n[patient]\nmrn = \"MRN-361411\"\nage = 61\ngender = \"M\"\n\n[vitals]\nbp = \"126/99\"\nhr = 78\ntemp_f = 102.4\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"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": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<assessment_id>ASMT-711127</assessment_id>\n<student_id>STU-193006</student_id>\n<course_id>CRS-9185</course_id>\n<type>assignment</type>\n<date>2026-01-01</date>\n<scores>\n<question>1</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>73</total_score>\n<percentage>59.24</percentage>\n<grade>A</grade>\n</student_assessment>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from XML to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nassessment_id: ASMT-711127\nstudent_id: STU-193006\ncourse_id: CRS-9185\ntype: assignment\ndate: '2026-01-01'\nscores:\n- question: 1\n points_earned: 0\n points_possible: 10\n- question: 2\n points_earned: 5\n points_possible: 10\n- question: 3\n points_earned: 1\n points_possible: 10\n- question: 4\n points_earned: 8\n points_possible: 10\n- question: 5\n points_earned: 7\n points_possible: 10\n- question: 6\n points_earned: 0\n points_possible: 10\n- question: 7\n points_earned: 3\n points_possible: 10\n- question: 8\n points_earned: 6\n points_possible: 10\n- question: 9\n points_earned: 9\n points_possible: 10\n- question: 10\n points_earned: 1\n points_possible: 10\ntotal_score: 73\npercentage: 59.24\ngrade: A\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 257
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<research_paper>\n<authors>\n<name>John Durham</name>\n<affiliation>Fletcher-Robinson</affiliation>\n<email>davidmitchell@example.com</email>\n</authors>\n<authors>\n<name>Kendra Patrick</name>\n<affiliation>Garrison Ltd</affiliation>\n<email>randymccoy@example.org</email>\n</authors>\n<authors>\n<name>Scott Maxwell</name>\n<affiliation>Rhodes, Hernandez and Fisher</affiliation>\n<email>tburns@example.net</email>\n</authors>\n<citations>325</citations>\n<funding_source />\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from XML to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nauthors:\n- name: John Durham\n affiliation: Fletcher-Robinson\n email: davidmitchell@example.com\n- name: Kendra Patrick\n affiliation: Garrison Ltd\n email: randymccoy@example.org\n- name: Scott Maxwell\n affiliation: Rhodes, Hernandez and Fisher\n email: tburns@example.net\ncitations: 325\nfunding_source: null\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 157
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<result_id>LAB-5820682</result_id>\n<patient_mrn>MRN-869394</patient_mrn>\n<order_date>2026-01-06</order_date>\n<panel>CBC</panel>\n<results>\n<test>Glucose</test>\n<value>188.8</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>75.9</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>82.1</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>108.3</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>86.4</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n</lab_result>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 246
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from YAML to JSON:\ncourse_id: CRS-7100\ncode: LWT322\ntitle: Compatible eco-centric implementation 101\ninstructor: Samantha Webster\ncredits: 4\nterm: Fall 2023\nschedule:\n- week: 1\n topic: think\n- week: 2\n topic: research\n- week: 3\n topic: kitchen\n- week: 4\n topic: turn\n- week: 5\n topic: surface\n- week: 6\n topic: we\n- week: 7\n topic: fine\n- week: 8\n topic: little\n- week: 9\n topic: number\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from YAML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"course_id\": \"CRS-7100\",\n \"code\": \"LWT322\",\n \"title\": \"Compatible eco-centric implementation 101\",\n \"instructor\": \"Samantha Webster\",\n \"credits\": 4,\n \"term\": \"Fall 2023\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"think\"\n },\n {\n \"week\": 2,\n \"topic\": \"research\"\n },\n {\n \"week\": 3,\n \"topic\": \"kitchen\"\n },\n {\n \"week\": 4,\n \"topic\": \"turn\"\n },\n {\n \"week\": 5,\n \"topic\": \"surface\"\n },\n {\n \"week\": 6,\n \"topic\": \"we\"\n },\n {\n \"week\": 7,\n \"topic\": \"fine\"\n },\n {\n \"week\": 8,\n \"topic\": \"little\"\n },\n {\n \"week\": 9,\n \"topic\": \"number\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 268
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<parties>\n<name>Chapman-Valdez</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Martin, Torres and Berry</name>\n<role>party_b</role>\n</parties>\n<value>171312</value>\n<effective_date>2026-01-04</effective_date>\n<status>pending</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nparties:\n- name: Chapman-Valdez\n role: party_a\n- name: Martin, Torres and Berry\n role: party_b\nvalue: 171312\neffective_date: '2026-01-04'\nstatus: pending\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 117
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"review_id\": \"REV-8961737\",\n \"product_id\": \"PROD-948538\",\n \"user_id\": \"53577ef0-c025-458e-87cc-d92e62c31125\",\n \"rating\": 1,\n \"title\": \"Away throughout employee around position.\",\n \"content\": \"Red every recently you this spring skin present. Hour third group throw say than purpose by.\\nAway do nearly dream. Interest former wear also yourself myself. Far available pick.\",\n \"date\": \"2026-01-03\",\n \"verified_purchase\": false,\n \"helpful_votes\": 15\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-8961737</review_id>\n<product_id>PROD-948538</product_id>\n<user_id>53577ef0-c025-458e-87cc-d92e62c31125</user_id>\n<rating>1</rating>\n<title>Away throughout employee around position.</title>\n<content>Red every recently you this spring skin present. Hour third group throw say than purpose by.\nAway do nearly dream. Interest former wear also yourself myself. Far available pick.</content>\n<date>2026-01-03</date>\n<verified_purchase>False</verified_purchase>\n<helpful_votes>15</helpful_votes>\n</customer_review>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 224
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this YAML data into JSON format:\ncompany: Perez, Luna and Martin\nticker: STKF\nquarter: Q1 2020\nrevenue: 74600917\nexpenses: 27659803\nnet_income: 7949721\neps: 7.26\nmetrics:\n profit_margin: 16.38\n roe: 8.11\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from YAML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"company\": \"Perez, Luna and Martin\",\n \"ticker\": \"STKF\",\n \"quarter\": \"Q1 2020\",\n \"revenue\": 74600917,\n \"expenses\": 27659803,\n \"net_income\": 7949721,\n \"eps\": 7.26,\n \"metrics\": {\n \"profit_margin\": 16.38,\n \"roe\": 8.11\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": "Output news article as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id: ART-1929345\nheadline: Operative exuding process improvement\nauthor: Jonathan Bray\npublished: '2026-01-04T11:58:45.141825'\nsection: Politics\ncontent: 'Us happen beautiful modern arm hope. Best southern let out use and thus\n approach.\n\n Court pass run degree. Party ten goal dream hear dark activity.\n\n Really fly brother when together training bag. Significant major skill after family\n style.'\ntags:\n- thought\n- education\n- 'no'\n- particularly\nviews: 80295\nshares: 1283\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 199
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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:\nexperiment_id = \"EXP-594884\"\ntitle = \"Effect of central on play\"\nconclusion = \"non-significant\"\n[[results]]\nmetric = \"efficacy\"\nbaseline = 15.62\nendpoint = 62.06\np_value = 0.0386\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 53.3\nendpoint = 13.92\np_value = 0.0809\n\n[[results]]\nmetric = \"safety\"\nbaseline = 64.01\nendpoint = 59.53\np_value = 0.3673\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 45.14\nendpoint = 49.39\np_value = 0.4568\n\n[methodology]\ndesign = \"observational\"\nsample_size = 163\nduration_days = 335\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 201
} |
[
{
"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:\nassessment_id,course_id,date,grade,percentage,scores,student_id,total_score,type\r\nASMT-444476,,2026-01-01,,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 1, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 1, \"\"po\",,72,assignment\r\nASMT-265502,CRS-4435,2026-01-06,B,55.63,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 1, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 6, \"\"po\",STU-142509,56,assignment\r\nASMT-376012,CRS-9913,2026-01-06,C,66.06,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 4, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 9, \"\"po\",STU-377930,62,exam\r\nASMT-317403,CRS-7273,2026-01-03,A,54.26,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 10, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 8, \"\"p\",STU-959561,95,quiz\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 270
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output social media post as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id: POST-67423083\nplatform: twitter\nuser_id: 80ae6c09-afaf-4e18-a928-887d901005f9\nusername: laurawalker\ncontent: Positive because become school item only view. Wear three matter hand listen\n move lay federal. Two activity one author become.\ntimestamp: '2026-01-07T01:26:11.015086'\nhashtags:\n- '#itself'\n- '#enjoy'\nengagement:\n likes: 1855\n shares: 454\n comments: 9\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 172
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<prescriber>Charles Mccarthy</prescriber>\n<patient_mrn>MRN-134957</patient_mrn>\n<date>2026-01-06</date>\n<rx_id>RX-2370233</rx_id>\n</prescription>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from XML to YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nprescriber: Charles Mccarthy\npatient_mrn: MRN-134957\ndate: '2026-01-06'\nrx_id: RX-2370233\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 102
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<result_id>LAB-5820682</result_id>\n<patient_mrn>MRN-869394</patient_mrn>\n<order_date>2026-01-06</order_date>\n<panel>CBC</panel>\n<results>\n<test>Glucose</test>\n<value>188.8</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>75.9</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>82.1</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>108.3</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>86.4</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n</lab_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result from XML to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nresult_id: LAB-5820682\npatient_mrn: MRN-869394\norder_date: '2026-01-06'\npanel: CBC\nresults:\n- test: Glucose\n value: 188.8\n unit: g/dL\n flag: high\n- test: WBC\n value: 75.9\n unit: mg/dL\n flag: high\n- test: Glucose\n value: 82.1\n unit: mg/dL\n flag: normal\n- test: Glucose\n value: 108.3\n unit: mg/dL\n flag: high\n- test: WBC\n value: 86.4\n unit: g/dL\n flag: low\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "lab_result",
"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": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-235027</experiment_id>\n<title>Effect of personal on mouth</title>\n<conclusion>significant</conclusion>\n<results>\n<metric>safety</metric>\n<baseline>65.08</baseline>\n<endpoint>79.76</endpoint>\n<p_value>0.2187</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>70.95</baseline>\n<endpoint>63.23</endpoint>\n<p_value>0.0104</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>36.99</baseline>\n<endpoint>80.45</endpoint>\n<p_value>0.1853</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>14.55</baseline>\n<endpoint>99.7</endpoint>\n<p_value>0.2575</p_value>\n</results>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result 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 \"experiment_id\": \"EXP-235027\",\n \"title\": \"Effect of personal on mouth\",\n \"conclusion\": \"significant\",\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 65.08,\n \"endpoint\": 79.76,\n \"p_value\": 0.2187\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 70.95,\n \"endpoint\": 63.23,\n \"p_value\": 0.0104\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 36.99,\n \"endpoint\": 80.45,\n \"p_value\": 0.1853\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 14.55,\n \"endpoint\": 99.7,\n \"p_value\": 0.2575\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 225
} |
[
{
"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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Team-oriented client-driven contingency API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/section\": {\n \"get\": {\n \"summary\": \"Wait area whole alone affect gun process.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to XML\n2. Complexity: 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>Team-oriented client-driven contingency API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</section>\n<get>\n<summary>Wait area whole alone affect gun process.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param2</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//section>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 246
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate research paper data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npaper_id = \"arXiv:2023.24842\"\ntitle = \"Implemented impactful process improvement\"\nabstract = \"Quality charge your significant view evening.\\nCause send line fill throughout better change. Rich study computer sell cause.\"\nkeywords = [ \"bag\", \"institution\", \"throughout\", \"make\", \"discover\",]\ncitations = 154\nfunding_source = \"Jensen, Wall and Green\"\n[[authors]]\nname = \"Amy Patterson\"\naffiliation = \"Adams, Thompson and Jackson\"\nemail = \"elove@example.net\"\n\n[[authors]]\nname = \"Wanda Pearson\"\naffiliation = \"Franklin and Sons\"\nemail = \"tcaldwell@example.com\"\n\n[publication]\nvenue = \"Science\"\nyear = 2022\ndoi = \"10.1974/YyDY\"\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 230
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output customer review as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: 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:\nreview_id = \"REV-7709348\"\nproduct_id = \"PROD-841901\"\nuser_id = \"74259c00-dc65-4a27-acb3-efacc370f46c\"\nrating = 4\ntitle = \"Culture front even.\"\ncontent = \"Two produce finally act. Blood science it upon.\\nMillion bit capital have field during sound. Father human decade cultural audience common throw.\\nUnder design north keep water right. Too now field.\"\ndate = \"2026-01-03\"\nverified_purchase = true\nhelpful_votes = 96\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 179
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to YAML:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Mandatory secondary conglomeration API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/human\": {\n \"get\": {\n \"summary\": \"Ball billion home.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to YAML\n2. Complexity: 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:\nopenapi: 3.0.0\ninfo:\n title: Mandatory secondary conglomeration API\n version: 1.0.0\npaths:\n /human:\n get:\n summary: Ball billion home.\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": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 194
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output financial report as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Johnson and Sons\nticker: KEMA\nquarter: Q4 2023\nrevenue: 75428990\nexpenses: 78539059\nnet_income: 3132437\neps: 7.27\nmetrics:\n profit_margin: 26.59\n roe: 17.7\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 120
} |
[
{
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nVAQ490,CRS-7399,4,40,30,30,Tammy Griffith,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"media\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"chair\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"perhaps\"\"}, {\"\"we\",Fall 2024,Ameliorated explicit migration 101\r\nJBP383,CRS-1453,4,40,30,30,Steven Davis,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"set\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"firm\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"threat\"\"}, {\"\"week\"\":\",Spring 2022,Self-enabling reciprocal system engine 101\r\nDMP308,CRS-4662,3,40,30,30,Mark Green,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"detail\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"the\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"certain\"\"}, {\"\"wee\",Fall 2020,Compatible content-based frame 101\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 261
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Switchable contextually-based data-warehouse API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/various\": {\n \"get\": {\n \"summary\": \"Address near ok else.\",\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>Switchable contextually-based data-warehouse API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</various>\n<get>\n<summary>Address near ok else.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//various>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 222
} |
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id: POST-20396431\nplatform: twitter\nuser_id: 948c9e55-303c-455a-bfb9-0e83f8bbf896\nusername: curtismiller\ncontent: 'Writer from customer. Conference radio nation single before left watch.\n\n Test large least quality. Spring action Republican.'\ntimestamp: '2026-01-07T01:26:13.035394'\nhashtags:\n- '#measure'\n- '#fast'\nengagement:\n likes: 6083\n shares: 512\n comments: 16\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 172
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nQTY141,CRS-4188,3,40,30,30,Jenny Lucas,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"base\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"car\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"star\"\"}, {\"\"week\"\": 4\",Spring 2020,Sharable high-level complexity 101\r\nONG382,CRS-8452,4,40,30,30,Taylor Lee,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"decision\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"enjoy\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"need\"\"}, {\"\"we\",Spring 2022,Function-based multi-state throughput 101\r\nQQW405,CRS-6954,3,40,30,30,Jason Wallace,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"administration\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"human\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"real\"\"}\",Fall 2021,Mandatory object-oriented knowledge user 101\r\nBEH496,CRS-1223,4,40,30,30,Penny Daugherty,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"successful\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"example\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"to\"\"}, {\"\"\",Fall 2021,Quality-focused scalable data-warehouse 101\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from CSV to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"course_id\": \"CRS-4188\",\n \"code\": \"QTY141\",\n \"title\": \"Sharable high-level complexity 101\",\n \"instructor\": \"Jenny Lucas\",\n \"credits\": 3,\n \"term\": \"Spring 2020\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"base\"\n },\n {\n \"week\": 2,\n \"topic\": \"car\"\n },\n {\n \"week\": 3,\n \"topic\": \"star\"\n },\n {\n \"week\": 4,\n \"topic\": \"me\"\n },\n {\n \"week\": 5,\n \"topic\": \"because\"\n },\n {\n \"week\": 6,\n \"topic\": \"particular\"\n },\n {\n \"week\": 7,\n \"topic\": \"window\"\n },\n {\n \"week\": 8,\n \"topic\": \"memory\"\n },\n {\n \"week\": 9,\n \"topic\": \"rise\"\n },\n {\n \"week\": 10,\n \"topic\": \"manager\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 278
} |
[
{
"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-4851405\"\npatient_mrn = \"MRN-131088\"\norder_date = \"2026-01-06\"\npanel = \"CBC\"\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 166.3\nunit = \"mg/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 113.8\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 151.3\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 172.4\nunit = \"g/dL\"\nflag = \"low\"\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 169
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate course syllabus data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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<course_syllabus>\n<course_id>CRS-4915</course_id>\n<code>OPX182</code>\n<title>Customer-focused empowering orchestration 101</title>\n<instructor>Patricia Thomas</instructor>\n<credits>3</credits>\n<term>Fall 2020</term>\n<schedule>\n<week>1</week>\n<topic>interview</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>threat</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>process</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>against</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>easy</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>manager</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>experience</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>push</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>stage</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>may</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 317
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npaper_id: arXiv:2024.95466\ntitle: Monitored 4thgeneration array\nfunding_source: null\nkeywords:\n- nation\n- civil\n- civil\n- data\npublication:\n venue: Science\n year: 2020\n doi: 10.1762/IBqA\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "research_paper",
"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": "Create a JSON representation of clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-2778413\",\n \"patient\": {\n \"mrn\": \"MRN-949372\",\n \"age\": 62,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-05\",\n \"chief_complaint\": \"chest pain\",\n \"vitals\": {\n \"bp\": \"139/89\",\n \"hr\": 75,\n \"temp_f\": 100.6\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"K59\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J78\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from CSV to JSON:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\n\"Provide project number memory middle. Source full experience condition per north hit.\nMinute imagine\",\"[{\"\"name\"\": \"\"Philip Watkins\"\", \"\"affiliation\"\": \"\"Wang Group\"\", \"\"email\"\": \"\"millerjohn@example.com\"\"}, {\"\"name\"\"\",479,None,\"[\"\"station\"\", \"\"president\"\", \"\"painting\"\", \"\"news\"\"]\",arXiv:2020.62016,10.4215/LwgO,Science,2021,Triple-buffered multi-state database\r\n\"Important must benefit now design quality back degree.\nTrade step sing which. Certain show operation\",\"[{\"\"name\"\": \"\"Mark Miller\"\", \"\"affiliation\"\": \"\"Martin-Miller\"\", \"\"email\"\": \"\"elizabeth92@example.org\"\"}, {\"\"name\",412,None,\"[\"\"oil\"\", \"\"issue\"\", \"\"term\"\", \"\"difference\"\"]\",arXiv:2022.63393,10.6880/oYAT,Science,2024,Reduced analyzing software\r\n\"Color stay group may eat argue. Financial against ahead.\nMy term matter. Else most voice direction. \",\"[{\"\"name\"\": \"\"Andre Hardy\"\", \"\"affiliation\"\": \"\"Davis Inc\"\", \"\"email\"\": \"\"brett93@example.net\"\"}, {\"\"name\"\": \"\"Jaso\",437,\"Oliver, Stevens and Warren\",\"[\"\"grow\"\", \"\"ball\"\", \"\"conference\"\"]\",arXiv:2024.40490,10.9948/PXeL,Cell,2023,Advanced real-time conglomeration\r\nReceive list crime seem Congress military less. Region religious myself carry door subject movement.,\"[{\"\"name\"\": \"\"Melissa Brady\"\", \"\"affiliation\"\": \"\"Davis, Orr and Ramirez\"\", \"\"email\"\": \"\"carriemaynard@example.\",35,None,\"[\"\"off\"\", \"\"call\"\", \"\"admit\"\"]\",arXiv:2024.82032,10.1323/rItj,Science,2023,Open-architected client-driven definition\r\n\"Score media teach phone through. Music sort whether.\nEvent may parent lawyer forward others. Bill di\",\"[{\"\"name\"\": \"\"Barbara Vasquez\"\", \"\"affiliation\"\": \"\"Klein, Rogers and Terrell\"\", \"\"email\"\": \"\"natalie37@example\",293,Henderson and Sons,\"[\"\"face\"\", \"\"term\"\", \"\"front\"\", \"\"most\"\"]\",arXiv:2023.48601,10.1103/weHm,Nature,2020,Triple-buffered methodical forecast\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from CSV to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"paper_id\": \"arXiv:2020.62016\",\n \"title\": \"Triple-buffered multi-state database\",\n \"authors\": [\n {\n \"name\": \"Philip Watkins\",\n \"affiliation\": \"Wang Group\",\n \"email\": \"millerjohn@example.com\"\n },\n {\n \"name\": \"Joshua Coleman\",\n \"affiliation\": \"Sutton Inc\",\n \"email\": \"hgarcia@example.net\"\n }\n ],\n \"abstract\": \"Provide project number memory middle. Source full experience condition per north hit.\\nMinute imagine father. Trip community effect bag.\",\n \"keywords\": [\n \"station\",\n \"president\",\n \"painting\",\n \"news\"\n ],\n \"publication\": {\n \"venue\": \"Science\",\n \"year\": 2021,\n \"doi\": \"10.4215/LwgO\"\n },\n \"citations\": 479,\n \"funding_source\": null\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 257
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.