messages
listlengths 3
3
| metadata
dict |
|---|---|
[
{
"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:\nreview_id: REV-8045456\nproduct_id: PROD-463913\nuser_id: ba642a1e-c9a9-4bbb-9297-90eddc75d10f\nrating: 4\ntitle: Per responsibility past green trip.\ncontent: 'You woman when. Night collection whole officer along skin.\n\n Example against need. Likely you good effort. Billion design trouble special tree\n less tonight.'\ndate: '2026-01-05'\nverified_purchase: true\nhelpful_votes: 48\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review 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 \"review_id\": \"REV-8045456\",\n \"product_id\": \"PROD-463913\",\n \"user_id\": \"ba642a1e-c9a9-4bbb-9297-90eddc75d10f\",\n \"rating\": 4,\n \"title\": \"Per responsibility past green trip.\",\n \"content\": \"You woman when. Night collection whole officer along skin.\\nExample against need. Likely you good effort. Billion design trouble special tree less tonight.\",\n \"date\": \"2026-01-05\",\n \"verified_purchase\": true,\n \"helpful_votes\": 48\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 187
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output social media post as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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:\ncontent,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username\r\n\"Here represent fact her bill. Outside appear blue staff.\nAnything enough wear onto most cold add sco\",292,8160,568,\"[\"\"#culture\"\", \"\"#another\"\"]\",facebook,POST-82196429,2026-01-07T01:26:11.055244,715dc001-379a-4b95-a83a-374542f74640,johngalvan\r\nLetter key wear course cover near character. Wind pattern player explain side life. Huge purpose yea,301,5600,191,\"[\"\"#what\"\", \"\"#read\"\", \"\"#do\"\"]\",instagram,POST-80056165,2026-01-07T01:26:11.056104,be7871bf-9c3d-42fc-80ea-ed45f21aea55,tylersteve\r\nAgreement turn wait yet include able imagine. Interview trouble cover decision policy staff water se,438,1094,76,\"[\"\"#decision\"\", \"\"#stay\"\", \"\"#blood\"\"]\",twitter,POST-29254440,2026-01-07T01:26:11.056373,746257e3-71de-4abc-bab1-471edd9560b7,hinesjustin\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 293
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\nabstract,authors,citations,date,funding_source,grade,keywords,paper_id,publication_doi,publication_venue,publication_year,student_id,title,type\r\n,,,2026-01-05,,B,,,,,,STU-866146,,assignment\r\nQuality still impact investment. Light shake station real while off. Agreement call letter image reg,\"[{\"\"name\"\": \"\"Carol Ruiz\"\", \"\"affiliation\"\": \"\"Huerta LLC\"\", \"\"email\"\": \"\"mroberts@example.com\"\"}, {\"\"name\"\": \"\"Jil\",148,,None,,\"[\"\"computer\"\", \"\"season\"\", \"\"true\"\"]\",arXiv:2023.78946,10.6661/yHNc,Cell,2024,,Synergistic executive policy,\r\nConcern note senior herself red south. Identify same officer still relate.,\"[{\"\"name\"\": \"\"Susan Turner\"\", \"\"affiliation\"\": \"\"Sweeney-Hayes\"\", \"\"email\"\": \"\"vincent36@example.org\"\"}, {\"\"name\"\"\",57,,None,,\"[\"\"tonight\"\", \"\"heart\"\", \"\"quality\"\"]\",arXiv:2020.89455,10.6329/CciP,Science,2024,,Persistent intermediate access,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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 \"grade\": \"B\",\n \"type\": \"assignment\",\n \"student_id\": \"STU-866146\",\n \"date\": \"2026-01-05\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 105
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this CSV data into JSON format:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nVJN392,CRS-8625,3,40,30,30,Samuel Hernandez,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"still\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"sing\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"girl\"\"}, {\"\"week\"\":\",Fall 2020,Monitored dynamic challenge 101\r\nNRL134,CRS-1888,4,40,30,30,Lucas Johnson,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"thus\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"style\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"process\"\"}, {\"\"wee\",Fall 2023,Team-oriented fault-tolerant portal 101\r\nGMM309,CRS-5852,4,40,30,30,Jaime Briggs,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"next\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"conference\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"cover\"\"}, {\"\"\",Fall 2020,Public-key bottom-line 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-8625\",\n \"code\": \"VJN392\",\n \"title\": \"Monitored dynamic challenge 101\",\n \"instructor\": \"Samuel Hernandez\",\n \"credits\": 3,\n \"term\": \"Fall 2020\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"still\"\n },\n {\n \"week\": 2,\n \"topic\": \"sing\"\n },\n {\n \"week\": 3,\n \"topic\": \"girl\"\n },\n {\n \"week\": 4,\n \"topic\": \"thing\"\n },\n {\n \"week\": 5,\n \"topic\": \"report\"\n },\n {\n \"week\": 6,\n \"topic\": \"movement\"\n },\n {\n \"week\": 7,\n \"topic\": \"cost\"\n },\n {\n \"week\": 8,\n \"topic\": \"affect\"\n },\n {\n \"week\": 9,\n \"topic\": \"six\"\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": 264
}
|
[
{
"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 \"review_id\": \"REV-2274729\",\n \"product_id\": \"PROD-918326\",\n \"user_id\": \"26d02f17-4175-4f2c-b1d2-689e9a29b3e5\",\n \"rating\": 3,\n \"title\": \"Resource popular total threat ball.\",\n \"content\": \"House spend in street. Tv president work. Before thank standard tree away.\",\n \"date\": \"2026-01-06\",\n \"verified_purchase\": true,\n \"helpful_votes\": 61\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review 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:\nreview_id: REV-2274729\nproduct_id: PROD-918326\nuser_id: 26d02f17-4175-4f2c-b1d2-689e9a29b3e5\nrating: 3\ntitle: Resource popular total threat ball.\ncontent: House spend in street. Tv president work. Before thank standard tree away.\ndate: '2026-01-06'\nverified_purchase: true\nhelpful_votes: 61\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 152
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-712001</experiment_id>\n<title>Effect of history on even</title>\n<methodology>\n<design>observational</design>\n<sample_size>484</sample_size>\n<duration_days>211</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>98.35</baseline>\n<endpoint>69.67</endpoint>\n<p_value>0.3227</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>11.16</baseline>\n<endpoint>20.95</endpoint>\n<p_value>0.3458</p_value>\n</results>\n<conclusion>significant</conclusion>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"experiment_id\": \"EXP-712001\",\n \"title\": \"Effect of history on even\",\n \"methodology\": {\n \"design\": \"observational\",\n \"sample_size\": 484,\n \"duration_days\": 211\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 98.35,\n \"endpoint\": 69.67,\n \"p_value\": 0.3227\n },\n {\n \"metric\": \"efficacy\",\n \"baseline\": 11.16,\n \"endpoint\": 20.95,\n \"p_value\": 0.3458\n }\n ],\n \"conclusion\": \"significant\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 193
}
|
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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:\ncompany,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker\r\nEdwards-Mckay,,64840530,,,,Q2 2021,,GZHV\r\nBrown-Williams,1.19,18332927,10.29,11.75,4374968,Q4 2023,57782165,TMXY\r\nSilva-West,9.03,12601410,9.08,20.41,1275864,Q3 2021,41234785,WBMA\r\n\"Schwartz, Jimenez and Holt\",0.97,34860850,8.9,16.39,3500308,Q1 2021,85998143,ILEU\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 167
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"company\": \"Simmons, Bradford and Dixon\",\n \"ticker\": \"WBWB\",\n \"quarter\": \"Q1 2024\",\n \"revenue\": 53992092,\n \"expenses\": 64883264,\n \"net_income\": 16701857,\n \"eps\": 1.68,\n \"metrics\": {\n \"profit_margin\": 10.55,\n \"roe\": 13.33\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 138
}
|
[
{
"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:\ntxn_id: TXN-34939831\ncustomer_id: 2f7988da-c001-4d4e-850c-f99986363268\ntimestamp: '2026-01-07T01:26:15.010643'\nitems:\n- sku: SKU-52213\n qty: 5\n price: 230.78\n- sku: SKU-37815\n qty: 4\n price: 27.45\nsubtotal: 1760.58\ntax: 139.95\ntotal: 806.5\npayment_method: apple_pay\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record 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 \"txn_id\": \"TXN-34939831\",\n \"customer_id\": \"2f7988da-c001-4d4e-850c-f99986363268\",\n \"timestamp\": \"2026-01-07T01:26:15.010643\",\n \"items\": [\n {\n \"sku\": \"SKU-52213\",\n \"qty\": 5,\n \"price\": 230.78\n },\n {\n \"sku\": \"SKU-37815\",\n \"qty\": 4,\n \"price\": 27.45\n }\n ],\n \"subtotal\": 1760.58,\n \"tax\": 139.95,\n \"total\": 806.5,\n \"payment_method\": \"apple_pay\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 178
}
|
[
{
"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<contract_id>CTR-594897</contract_id>\n<parties>\n<name>Nguyen-Reeves</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Williams-Andrade</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-04</effective_date>\n<term_months>16</term_months>\n<value>736511</value>\n<status>executed</status>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ncontract_id: CTR-594897\nparties:\n- name: Nguyen-Reeves\n role: party_a\n- name: Williams-Andrade\n role: party_b\neffective_date: '2026-01-04'\nterm_months: 16\nvalue: 736511\nstatus: executed\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 124
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate error log data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"error_id\": \"b7c34b47-4e4a-4c41-888f-ff64a1b8d06d\",\n \"timestamp\": \"2026-01-07T01:26:14.918711\",\n \"level\": \"WARNING\",\n \"service\": \"discussService\",\n \"message\": \"Hot outside inside consumer test.\",\n \"stack_trace\": [\n \"at game.py:441\",\n \"at activity.py:14\",\n \"at administration.py:426\",\n \"at modern.py:89\"\n ],\n \"context\": {\n \"user_id\": \"e8605dad-78b4-4d4e-8061-41a780440a5f\",\n \"request_id\": \"77c8a2c4-4277-4222-81f1-817bd0da301c\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 192
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output product listing as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-442175\",\n \"name\": \"Phased real-time system engine\",\n \"category\": \"books\",\n \"price\": 748.72,\n \"currency\": \"USD\",\n \"stock\": 660,\n \"is_available\": true,\n \"rating\": 4.21,\n \"reviews\": 544,\n \"specs\": {\n \"weight_kg\": 42.73,\n \"dimensions\": \"32x58x41cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 150
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output lab result as XML."
},
{
"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-3958918</result_id>\n<patient_mrn>MRN-243411</patient_mrn>\n<order_date>2026-01-01</order_date>\n<panel>Lipid</panel>\n<results>\n<test>Glucose</test>\n<value>198.7</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>160.0</value>\n<unit>g/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>191.3</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>76.6</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>119.9</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>196.9</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": 272
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-888613\",\n \"name\": \"Multi-lateral attitude-oriented intranet\",\n \"category\": \"electronics\",\n \"price\": 967.86,\n \"currency\": \"USD\",\n \"stock\": 776,\n \"is_available\": true,\n \"rating\": 4.69,\n \"reviews\": 546,\n \"specs\": {\n \"weight_kg\": 5.82,\n \"dimensions\": \"66x50x71cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 154
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-460532</experiment_id>\n<title>Effect of data on kid</title>\n<methodology>\n<design>observational</design>\n<sample_size>482</sample_size>\n<duration_days>320</duration_days>\n</methodology>\n<results>\n<metric>efficacy</metric>\n<baseline>32.76</baseline>\n<endpoint>19.95</endpoint>\n<p_value>0.1938</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>34.66</baseline>\n<endpoint>72.26</endpoint>\n<p_value>0.255</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 222
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output prescription as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"patient_mrn\": \"MRN-976657\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 90\n },\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"daily\",\n \"quantity\": 60\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"TID\",\n \"quantity\": 90\n }\n ],\n \"rx_id\": \"RX-2060640\",\n \"date\": \"2026-01-04\",\n \"prescriber\": \"Kelly Smith\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 196
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output clinical note as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K89\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J24\"\"}, {\"\"problem\"\": \"\"\",fever,2026-01-01,CN-8992258,54,F,MRN-606207,94/81,68,102.7\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I18\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J98\"\"}, {\"\"problem\",chest pain,2026-01-03,CN-2359709,48,M,MRN-481306,124/82,101,100.7\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"K32\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I10\"\"}]\",chest pain,2026-01-02,CN-1114707,54,M,MRN-219432,129/85,95,100.8\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J47\"\"}]\",fever,2026-01-06,CN-5363960,87,F,MRN-394080,111/105,65,102.6\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J58\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I91\"\"}, {\"\"problem\",headache,2026-01-06,CN-2468871,25,M,MRN-436731,150/70,76,97.4\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 318
}
|
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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:\nopenapi: 3.0.0\ninfo:\n title: Enterprise-wide solution-oriented circuit API\n version: 1.0.0\npaths:\n /several:\n get:\n summary: Painting space all five we exactly now.\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": "generation",
"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": "Produce a XML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>744374e9-663a-4ac9-8a1c-08e4745c208c</error_id>\n<timestamp>2026-01-07T01:26:14.535166</timestamp>\n<level>ERROR</level>\n<service>democraticService</service>\n<message>View product product over catch experience recognize politics.</message>\n<stack_trace>at give.py:400</stack_trace>\n<stack_trace>at play.py:27</stack_trace>\n<stack_trace>at husband.py:365</stack_trace>\n<stack_trace>at wide.py:107</stack_trace>\n<context>\n<user_id>47acb10a-4af3-41a3-83fb-c4de3fd3b428</user_id>\n<request_id>2abb359a-e44f-4207-b2a4-3962374766e8</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 230
}
|
[
{
"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:\nnote_id: CN-7319440\npatient:\n mrn: MRN-220534\n age: 24\n gender: M\nencounter_date: '2026-01-02'\nchief_complaint: headache\nvitals:\n bp: 94/79\n hr: 69\n temp_f: 100.9\nassessment:\n- problem: diabetes\n icd10: I20\n- problem: diabetes\n icd10: I97\n- problem: diabetes\n icd10: K28\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note 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 \"note_id\": \"CN-7319440\",\n \"patient\": {\n \"mrn\": \"MRN-220534\",\n \"age\": 24,\n \"gender\": \"M\"\n },\n \"encounter_date\": \"2026-01-02\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"94/79\",\n \"hr\": 69,\n \"temp_f\": 100.9\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"I20\"\n },\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"I97\"\n },\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"K28\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 193
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output course syllabus as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus 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:\ncourse_id = \"CRS-6287\"\ncode = \"PQX165\"\ntitle = \"Persevering contextually-based access 101\"\ninstructor = \"Matthew Ochoa\"\ncredits = 3\nterm = \"Fall 2023\"\n[[schedule]]\nweek = 1\ntopic = \"decide\"\n\n[[schedule]]\nweek = 2\ntopic = \"bed\"\n\n[[schedule]]\nweek = 3\ntopic = \"he\"\n\n[[schedule]]\nweek = 4\ntopic = \"game\"\n\n[[schedule]]\nweek = 5\ntopic = \"argue\"\n\n[[schedule]]\nweek = 6\ntopic = \"reality\"\n\n[[schedule]]\nweek = 7\ntopic = \"financial\"\n\n[[schedule]]\nweek = 8\ntopic = \"gun\"\n\n[[schedule]]\nweek = 9\ntopic = \"choose\"\n\n[[schedule]]\nweek = 10\ntopic = \"wonder\"\n\n[[schedule]]\nweek = 11\ntopic = \"soon\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 232
}
|
[
{
"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<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>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"paper_id\": \"arXiv:2021.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}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 256
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in YAML\n2. Complexity: 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:\nchannels:\n- name: online\n revenue: 3551886\n growth: 12.15\n- name: wholesale\n revenue: 3092274\n growth: 44.44\nunits_sold: 56571\ntop_products:\n- sku: SKU-1355\n sales: 430447\n- sku: SKU-5266\n sales: 422854\n- sku: SKU-9551\n sales: 330001\nperiod: May 2022\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "sales_analytics",
"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": "Produce a JSON document for a lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab 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 \"result_id\": \"LAB-4851405\",\n \"patient_mrn\": \"MRN-131088\",\n \"order_date\": \"2026-01-06\",\n \"panel\": \"CBC\",\n \"results\": [\n {\n \"test\": \"Hemoglobin\",\n \"value\": 166.3,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 113.8,\n \"unit\": \"g/dL\",\n \"flag\": \"normal\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 151.3,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 172.4,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 213
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output sales analytics as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in TOML\n2. Complexity: 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:\nperiod = \"February 2021\"\ntotal_revenue = 8378246\nunits_sold = 93488\n[[channels]]\nname = \"wholesale\"\nrevenue = 607218\ngrowth = 20.61\n\n[[channels]]\nname = \"retail\"\nrevenue = 1689719\ngrowth = 37.88\n\n[[top_products]]\nsku = \"SKU-7170\"\nsales = 157136\n\n[[top_products]]\nsku = \"SKU-3905\"\nsales = 484679\n\n[[top_products]]\nsku = \"SKU-5721\"\nsales = 207063\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 160
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output api specification as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Mandatory secondary conglomeration API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</human>\n<get>\n<summary>Ball billion home.</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<//human>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 237
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"paper_id\": \"arXiv:2021.14502\",\n \"title\": \"Intuitive client-driven implementation\",\n \"authors\": [\n {\n \"name\": \"Kelly Carter\",\n \"affiliation\": \"Duran, Morgan and Wise\",\n \"email\": \"fgrimes@example.org\"\n },\n {\n \"name\": \"Carolyn Summers\",\n \"affiliation\": \"Adams-Baker\",\n \"email\": \"xharris@example.org\"\n },\n {\n \"name\": \"Ana Stephenson\",\n \"affiliation\": \"Miller, Terrell and Campbell\",\n \"email\": \"andrew74@example.com\"\n }\n ],\n \"abstract\": \"Bank interesting partner prevent reality family. Political human either impact newspaper yet quite.\",\n \"keywords\": [\n \"join\",\n \"would\",\n \"agree\",\n \"effort\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2022,\n \"doi\": \"10.9639/GJNc\"\n },\n \"citations\": 472,\n \"funding_source\": \"Contreras, May and Miranda\"\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.14502</paper_id>\n<title>Intuitive client-driven implementation</title>\n<authors>\n<name>Kelly Carter</name>\n<affiliation>Duran, Morgan and Wise</affiliation>\n<email>fgrimes@example.org</email>\n</authors>\n<authors>\n<name>Carolyn Summers</name>\n<affiliation>Adams-Baker</affiliation>\n<email>xharris@example.org</email>\n</authors>\n<authors>\n<name>Ana Stephenson</name>\n<affiliation>Miller, Terrell and Campbell</affiliation>\n<email>andrew74@example.com</email>\n</authors>\n<abstract>Bank interesting partner prevent reality family. Political human either impact newspaper yet quite.</abstract>\n<keywords>join</keywords>\n<keywords>would</keywords>\n<keywords>agree</keywords>\n<keywords>effort</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2022</year>\n<doi>10.9639/GJNc</doi>\n</publication>\n<citations>472</citations>\n<funding_source>Contreras, May and Miranda</funding_source>\n</research_paper>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 321
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"December 2023\",\n \"total_revenue\": 1597601,\n \"units_sold\": 56983,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 896896,\n \"growth\": 15.43\n },\n {\n \"name\": \"online\",\n \"revenue\": 523152,\n \"growth\": 2.65\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-1038\",\n \"sales\": 399837\n },\n {\n \"sku\": \"SKU-4191\",\n \"sales\": 178310\n },\n {\n \"sku\": \"SKU-5950\",\n \"sales\": 53657\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"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": "Output clinical note as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nnote_id: CN-2305356\npatient:\n mrn: MRN-275296\n age: 85\n gender: M\nencounter_date: '2026-01-02'\nchief_complaint: headache\nvitals:\n bp: 162/98\n hr: 103\n temp_f: 97.9\nassessment:\n- problem: diabetes\n icd10: I73\n- problem: hypertension\n icd10: I70\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 140
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<stack_trace>at play.py:21</stack_trace>\n<stack_trace>at space.py:166</stack_trace>\n<stack_trace>at public.py:493</stack_trace>\n<stack_trace>at government.py:462</stack_trace>\n<error_id>dece4525-b43a-42c0-bd19-590427aeb5ca</error_id>\n<service>wrongService</service>\n<message>Too daughter color draw role.</message>\n<context>\n<user_id>13bdf80c-dec5-4389-9c68-b3142ee30270</user_id>\n<request_id>585587b7-59eb-45b4-83bd-d58fe462800c</request_id>\n</context>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"stack_trace\": [\n \"at play.py:21\",\n \"at space.py:166\",\n \"at public.py:493\",\n \"at government.py:462\"\n ],\n \"error_id\": \"dece4525-b43a-42c0-bd19-590427aeb5ca\",\n \"service\": \"wrongService\",\n \"message\": \"Too daughter color draw role.\",\n \"context\": {\n \"user_id\": \"13bdf80c-dec5-4389-9c68-b3142ee30270\",\n \"request_id\": \"585587b7-59eb-45b4-83bd-d58fe462800c\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"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": "Transform this YAML data into JSON format:\nperiod: November 2024\ntotal_revenue: 2676189\nunits_sold: 83309\nchannels:\n- name: online\n revenue: 3563016\n growth: 23.93\n- name: wholesale\n revenue: 4310802\n growth: 22.7\ntop_products:\n- sku: SKU-6301\n sales: 28890\n- sku: SKU-7925\n sales: 186307\n- sku: SKU-7802\n sales: 163007\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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 \"period\": \"November 2024\",\n \"total_revenue\": 2676189,\n \"units_sold\": 83309,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 3563016,\n \"growth\": 23.93\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 4310802,\n \"growth\": 22.7\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6301\",\n \"sales\": 28890\n },\n {\n \"sku\": \"SKU-7925\",\n \"sales\": 186307\n },\n {\n \"sku\": \"SKU-7802\",\n \"sales\": 163007\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 199
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"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<currency>USD</currency>\n<specs>\n<weight_kg>43.4</weight_kg>\n<dimensions>59x69x33cm</dimensions>\n</specs>\n<product_id>PROD-983904</product_id>\n<name>Managed radical time-frame</name>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "product_listing",
"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 social media post as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"post_id\": \"POST-85357806\",\n \"platform\": \"twitter\",\n \"user_id\": \"ddc85801-1812-4570-973f-602483eff9a7\",\n \"username\": \"wsanchez\",\n \"content\": \"Nature poor she reason travel protect. Meet myself than wind. Thank walk probably partner on far kitchen alone.\",\n \"timestamp\": \"2026-01-07T01:26:13.493861\",\n \"hashtags\": [\n \"#pressure\",\n \"#table\",\n \"#tell\",\n \"#in\"\n ],\n \"engagement\": {\n \"likes\": 3805,\n \"shares\": 40,\n \"comments\": 13\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 194
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output error log as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in JSON\n2. Complexity: 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 \"error_id\": \"a746d9d4-dc7d-4eea-ae60-7a4c8e50b982\",\n \"timestamp\": \"2026-01-07T01:26:12.011724\",\n \"level\": \"WARNING\",\n \"service\": \"untilService\",\n \"message\": \"See herself very kid decade candidate.\",\n \"stack_trace\": [\n \"at truth.py:153\",\n \"at deep.py:218\"\n ],\n \"context\": {\n \"user_id\": \"678438e5-a324-4181-8a56-7ab4d6bcae4a\",\n \"request_id\": \"85f2f874-a69d-43c6-9635-13f11ff993d0\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 178
}
|
[
{
"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<prescription>\n<rx_id>RX-7115760</rx_id>\n<patient_mrn>MRN-628534</patient_mrn>\n<prescriber>Kelly Yang</prescriber>\n<date>2026-01-04</date>\n<medications>\n<name>Metformin</name>\n<dosage>10mg</dosage>\n<frequency>daily</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription 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:\nrx_id: RX-7115760\npatient_mrn: MRN-628534\nprescriber: Kelly Yang\ndate: '2026-01-04'\nmedications:\n- name: Metformin\n dosage: 10mg\n frequency: daily\n quantity: 30\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 119
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I79\"\"}]\",chest pain,2026-01-01,CN-2778090,63,F,MRN-510097,113/64,101,102.8\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I38\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K80\"\"}, {\"\"problem\"\": \"\"\",headache,2026-01-01,CN-5664897,53,F,MRN-457857,166/87,117,100.7\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K25\"\"}]\",fever,2026-01-05,CN-5671614,28,F,MRN-356781,100/102,118,97.9\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J53\"\"}]\",chest pain,2026-01-05,CN-2572096,77,M,MRN-883252,162/66,73,99.1\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I28\"\"}]\",fever,2026-01-05,CN-5025250,69,M,MRN-713623,96/96,90,98.5\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 272
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"error_id\": \"a746d9d4-dc7d-4eea-ae60-7a4c8e50b982\",\n \"timestamp\": \"2026-01-07T01:26:12.011724\",\n \"level\": \"WARNING\",\n \"service\": \"untilService\",\n \"message\": \"See herself very kid decade candidate.\",\n \"stack_trace\": [\n \"at truth.py:153\",\n \"at deep.py:218\"\n ],\n \"context\": {\n \"user_id\": \"678438e5-a324-4181-8a56-7ab4d6bcae4a\",\n \"request_id\": \"85f2f874-a69d-43c6-9635-13f11ff993d0\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>a746d9d4-dc7d-4eea-ae60-7a4c8e50b982</error_id>\n<timestamp>2026-01-07T01:26:12.011724</timestamp>\n<level>WARNING</level>\n<service>untilService</service>\n<message>See herself very kid decade candidate.</message>\n<stack_trace>at truth.py:153</stack_trace>\n<stack_trace>at deep.py:218</stack_trace>\n<context>\n<user_id>678438e5-a324-4181-8a56-7ab4d6bcae4a</user_id>\n<request_id>85f2f874-a69d-43c6-9635-13f11ff993d0</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 204
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in XML\n2. Complexity: 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<experiment_result>\n<title>Effect of citizen on strong</title>\n<conclusion>significant</conclusion>\n<experiment_id>EXP-459167</experiment_id>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 129
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output contract as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"contract_id\": \"CTR-933130\",\n \"parties\": [\n {\n \"name\": \"Jackson Ltd\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Jimenez and Sons\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-05\",\n \"term_months\": 13,\n \"value\": 840226,\n \"status\": \"pending\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 148
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate prescription data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-9272435\",\n \"patient_mrn\": \"MRN-433695\",\n \"prescriber\": \"Beverly Lee\",\n \"date\": \"2026-01-06\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"daily\",\n \"quantity\": 60\n },\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 196
}
|
[
{
"role": "system",
"content": "You are an expert in 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<research_paper>\n<paper_id>arXiv:2021.59033</paper_id>\n<title>Secured analyzing Graphic Interface</title>\n<authors>\n<name>Jaime Wilkerson</name>\n<affiliation>Barber-Moore</affiliation>\n<email>iberry@example.com</email>\n</authors>\n<authors>\n<name>James Wiggins</name>\n<affiliation>Ellis, Lewis and Pierce</affiliation>\n<email>matthewgarrison@example.net</email>\n</authors>\n<authors>\n<name>Nicole Patterson</name>\n<affiliation>Smith Inc</affiliation>\n<email>amber32@example.org</email>\n</authors>\n<abstract>Town clear movie difference star. Finally yet rate so always arrive. Present foot off although fight business. Range peace will along early page.</abstract>\n<keywords>people</keywords>\n<keywords>stay</keywords>\n<keywords>election</keywords>\n<keywords>himself</keywords>\n<publication>\n<venue>Nature</venue>\n<year>2024</year>\n<doi>10.3586/YIpH</doi>\n</publication>\n<citations>445</citations>\n<funding_source>Jackson and Sons</funding_source>\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"paper_id\": \"arXiv:2021.59033\",\n \"title\": \"Secured analyzing Graphic Interface\",\n \"authors\": [\n {\n \"name\": \"Jaime Wilkerson\",\n \"affiliation\": \"Barber-Moore\",\n \"email\": \"iberry@example.com\"\n },\n {\n \"name\": \"James Wiggins\",\n \"affiliation\": \"Ellis, Lewis and Pierce\",\n \"email\": \"matthewgarrison@example.net\"\n },\n {\n \"name\": \"Nicole Patterson\",\n \"affiliation\": \"Smith Inc\",\n \"email\": \"amber32@example.org\"\n }\n ],\n \"abstract\": \"Town clear movie difference star. Finally yet rate so always arrive. Present foot off although fight business. Range peace will along early page.\",\n \"keywords\": [\n \"people\",\n \"stay\",\n \"election\",\n \"himself\"\n ],\n \"publication\": {\n \"venue\": \"Nature\",\n \"year\": 2024,\n \"doi\": \"10.3586/YIpH\"\n },\n \"citations\": 445,\n \"funding_source\": \"Jackson and Sons\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 296
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate product listing data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-602506</product_id>\n<name>Diverse 5thgeneration monitoring</name>\n<category>electronics</category>\n<price>469.91</price>\n<currency>USD</currency>\n<stock>372</stock>\n<is_available>True</is_available>\n<rating>3.7</rating>\n<reviews>813</reviews>\n<specs>\n<weight_kg>26.31</weight_kg>\n<dimensions>49x82x12cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 181
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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:\ncontract_id: CTR-323276\neffective_date: '2026-01-06'\nterm_months: 56\nstatus: pending\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 98
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this CSV data into JSON format:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nelectronics,USD,True,Decentralized mobile framework,654.79,PROD-877409,3.88,74,82x76x89cm,22.25,219\r\nbooks,USD,True,Ergonomic solution-oriented strategy,143.49,PROD-709411,2.7,505,48x60x14cm,39.69,761\r\nbooks,USD,True,Cloned systematic capability,801.72,PROD-127292,2.0,891,67x15x11cm,49.9,168\r\nclothing,USD,True,Cross-group cohesive matrix,735.84,PROD-686979,4.29,173,48x57x48cm,40.69,663\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from CSV to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"product_id\": \"PROD-877409\",\n \"name\": \"Decentralized mobile framework\",\n \"category\": \"electronics\",\n \"price\": 654.79,\n \"currency\": \"USD\",\n \"stock\": 219,\n \"is_available\": true,\n \"rating\": 3.88,\n \"reviews\": 74,\n \"specs\": {\n \"weight_kg\": 22.25,\n \"dimensions\": \"82x76x89cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 153
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in JSON\n2. Complexity: 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-122198\",\n \"title\": \"Effect of my on want\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 67,\n \"duration_days\": 212\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 74.69,\n \"endpoint\": 66.28,\n \"p_value\": 0.1604\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 61.46,\n \"endpoint\": 51.51,\n \"p_value\": 0.1869\n }\n ],\n \"conclusion\": \"significant\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"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 student assessment data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\nassessment_id = \"ASMT-626485\"\nstudent_id = \"STU-591114\"\ncourse_id = \"CRS-4230\"\ntype = \"assignment\"\ndate = \"2026-01-03\"\ntotal_score = 56\npercentage = 92.13\ngrade = \"A\"\n[[scores]]\nquestion = 1\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 8\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 11\npoints_earned = 8\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 293
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-3966060</rx_id>\n<patient_mrn>MRN-866595</patient_mrn>\n<prescriber>Vanessa Hull</prescriber>\n<date>2026-01-06</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>5mg</dosage>\n<frequency>daily</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Metformin</name>\n<dosage>10mg</dosage>\n<frequency>daily</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"rx_id\": \"RX-3966060\",\n \"patient_mrn\": \"MRN-866595\",\n \"prescriber\": \"Vanessa Hull\",\n \"date\": \"2026-01-06\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"5mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"10mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"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": "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-585291</assessment_id>\n<student_id>STU-482043</student_id>\n<course_id>CRS-2271</course_id>\n<type>quiz</type>\n<date>2026-01-02</date>\n<scores>\n<question>1</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>67</total_score>\n<percentage>58.64</percentage>\n<grade>C</grade>\n</student_assessment>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 438
}
|
[
{
"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: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-745521</product_id>\n<name>Visionary context-sensitive knowledgebase</name>\n<category>clothing</category>\n<price>971.77</price>\n<currency>USD</currency>\n<stock>251</stock>\n<is_available>True</is_available>\n<rating>2.58</rating>\n<reviews>649</reviews>\n<specs>\n<weight_kg>7.88</weight_kg>\n<dimensions>19x17x70cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 183
}
|
[
{
"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-460532\"\ntitle = \"Effect of data on kid\"\nconclusion = \"non-significant\"\n[[results]]\nmetric = \"efficacy\"\nbaseline = 32.76\nendpoint = 19.95\np_value = 0.1938\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 34.66\nendpoint = 72.26\np_value = 0.255\n\n[methodology]\ndesign = \"observational\"\nsample_size = 482\nduration_days = 320\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 158
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate news article data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<views>46235</views>\n<content>Ago among next follow market Democrat. Relate force party event benefit.\nBetween director concern involve trouble reason. Laugh officer whatever behind natural return social black. Course during father pull process level.</content>\n<shares>4037</shares>\n<published>2026-01-01T00:50:45.476654</published>\n<article_id>ART-9587405</article_id>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 187
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-394543</product_id>\n<name>Switchable secondary algorithm</name>\n<category>books</category>\n<price>736.63</price>\n<currency>USD</currency>\n<stock>392</stock>\n<is_available>True</is_available>\n<rating>1.5</rating>\n<reviews>650</reviews>\n<specs>\n<weight_kg>26.44</weight_kg>\n<dimensions>92x71x99cm</dimensions>\n</specs>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 180
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate api specification data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Managed client-server database API\"\nversion = \"1.0.0\"\n\n[paths.\"/possible\".get]\nsummary = \"Alone we say particularly police.\"\n[[paths.\"/possible\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/possible\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/possible\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/possible\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 189
}
|
[
{
"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:\narticle_id: ART-1845067\nheadline: Integrated real-time parallelism\nauthor: Casey Thomas\npublished: '2026-01-01T00:28:18.999988'\nsection: Politics\ncontent: 'Learn wall claim around say let parent exist. Home almost voice guy who.\n Hit away never and where.\n\n People music report care. Other let physical determine the game final during. His\n difficult woman painting pull pay able.'\ntags:\n- floor\n- general\n- send\n- standard\n- like\nviews: 81878\nshares: 1964\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article 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 \"article_id\": \"ART-1845067\",\n \"headline\": \"Integrated real-time parallelism\",\n \"author\": \"Casey Thomas\",\n \"published\": \"2026-01-01T00:28:18.999988\",\n \"section\": \"Politics\",\n \"content\": \"Learn wall claim around say let parent exist. Home almost voice guy who. Hit away never and where.\\nPeople music report care. Other let physical determine the game final during. His difficult woman painting pull pay able.\",\n \"tags\": [\n \"floor\",\n \"general\",\n \"send\",\n \"standard\",\n \"like\"\n ],\n \"views\": 81878,\n \"shares\": 1964\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 213
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output lab result as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in YAML\n2. Complexity: 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:\nresult_id: LAB-4340614\npatient_mrn: MRN-525256\norder_date: '2026-01-05'\npanel: CMP\nresults:\n- test: Glucose\n value: 99.4\n unit: mg/dL\n flag: high\n- test: Hemoglobin\n value: 160.7\n unit: mg/dL\n flag: high\n- test: Hemoglobin\n value: 89.7\n unit: mg/dL\n flag: normal\n- test: Glucose\n value: 194.3\n unit: g/dL\n flag: normal\n- test: Hemoglobin\n value: 95.6\n unit: mg/dL\n flag: normal\n- test: Hemoglobin\n value: 64.1\n unit: g/dL\n flag: normal\n- test: Hemoglobin\n value: 171.1\n unit: mg/dL\n flag: low\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "lab_result",
"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 \"views\": 59537,\n \"article_id\": \"ART-2017273\",\n \"tags\": [\n \"away\",\n \"adult\",\n \"happen\",\n \"adult\"\n ],\n \"author\": \"Craig Chen\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<views>59537</views>\n<article_id>ART-2017273</article_id>\n<tags>away</tags>\n<tags>adult</tags>\n<tags>happen</tags>\n<tags>adult</tags>\n<author>Craig Chen</author>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 137
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate news article data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\narticle_id = \"ART-6226138\"\nheadline = \"Innovative scalable concept\"\nauthor = \"Anthony Ewing\"\npublished = \"2026-01-01T17:49:33.715680\"\nsection = \"Politics\"\ncontent = \"Easy happen attention event top result season effect. Fear manage responsibility who health speech prevent.\\nClose pressure three as old. Yeah tough growth class possible. Series conference little challenge still manage.\"\ntags = [ \"arrive\", \"one\", \"something\", \"mouth\", \"child\",]\nviews = 89221\nshares = 262\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 192
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-02,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Metformin\"\", \"\"\",MRN-165132,Wayne Rich,RX-6254240\r\n2026-01-04,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 90}]\",MRN-285533,Kathryn Jones,RX-9842060\r\n2026-01-01,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Lisinopril\",MRN-968135,Elizabeth Dunn,RX-7108454\r\n2026-01-05,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 60}]\",MRN-116591,Patrick Harper,RX-3207713\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 244
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output student assessment as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ngrade = \"C\"\npercentage = 81.64\n[[scores]]\nquestion = 1\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 9\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 196
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-2341215\",\n \"patient_mrn\": \"MRN-901842\",\n \"prescriber\": \"Jerome Miller\",\n \"date\": \"2026-01-06\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"5mg\",\n \"frequency\": \"daily\",\n \"quantity\": 60\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 90\n },\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 90\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 196
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output api specification as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification 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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Down-sized exuding collaboration API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/smile\": {\n \"get\": {\n \"summary\": \"Total ago fight meet still not notice.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 218
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output research paper as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npaper_id = \"arXiv:2021.87295\"\ntitle = \"Centralized demand-driven data-warehouse\"\nabstract = \"View prevent key money institution.\"\nkeywords = [ \"away\", \"sign\", \"skill\", \"care\",]\ncitations = 14\nfunding_source = \"Edwards PLC\"\n[[authors]]\nname = \"Megan Casey DDS\"\naffiliation = \"Brock LLC\"\nemail = \"erinallison@example.net\"\n\n[[authors]]\nname = \"Matthew Meadows\"\naffiliation = \"Gardner, Summers and Taylor\"\nemail = \"summersrobert@example.com\"\n\n[publication]\nvenue = \"Nature\"\nyear = 2023\ndoi = \"10.6925/yHaK\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 199
}
|
[
{
"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<product_listing>\n<product_id>PROD-289583</product_id>\n<name>Business-focused 5thgeneration forecast</name>\n<category>books</category>\n<price>610.09</price>\n<currency>USD</currency>\n<stock>308</stock>\n<is_available>True</is_available>\n<rating>4.38</rating>\n<reviews>635</reviews>\n<specs>\n<weight_kg>45.28</weight_kg>\n<dimensions>49x22x48cm</dimensions>\n</specs>\n</product_listing>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from XML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nproduct_id: PROD-289583\nname: Business-focused 5thgeneration forecast\ncategory: books\nprice: 610.09\ncurrency: USD\nstock: 308\nis_available: true\nrating: 4.38\nreviews: 635\nspecs:\n weight_kg: 45.28\n dimensions: 49x22x48cm\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 134
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-9666876\npatient_mrn: MRN-499732\nprescriber: Stacy Allen\ndate: '2026-01-03'\nmedications:\n- name: Lisinopril\n dosage: 10mg\n frequency: TID\n quantity: 60\n- name: Metformin\n dosage: 10mg\n frequency: BID\n quantity: 60\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 134
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate experiment result data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-306589</experiment_id>\n<title>Effect of visit on society</title>\n<methodology>\n<design>cohort</design>\n<sample_size>865</sample_size>\n<duration_days>121</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>37.56</baseline>\n<endpoint>13.37</endpoint>\n<p_value>0.2469</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>17.57</baseline>\n<endpoint>90.05</endpoint>\n<p_value>0.455</p_value>\n</results>\n<results>\n<metric>efficacy</metric>\n<baseline>61.87</baseline>\n<endpoint>90.99</endpoint>\n<p_value>0.1315</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 252
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<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 JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"prescriber\": \"Charles Mccarthy\",\n \"patient_mrn\": \"MRN-134957\",\n \"date\": \"2026-01-06\",\n \"rx_id\": \"RX-2370233\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 109
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/fear_get_parameters,paths_/fear_get_responses_200_description,paths_/fear_get_responses_400_description,paths_/fear_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Phased clear-thinking complexity API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Position newspaper write worker.,,,,\r\nHistory impact beat morning. Ask bed day will allow. Prove because argue radio.,\"[{\"\"name\"\": \"\"Ronald Griffin\"\", \"\"affiliation\"\": \"\"Wright, Leon and Johnson\"\", \"\"email\"\": \"\"rparker@example.net\",338,None,,,\"[\"\"too\"\", \"\"senior\"\", \"\"full\"\", \"\"street\"\"]\",,arXiv:2022.27811,,,,,10.4926/phGW,Science,2024,Centralized empowering attitude\r\nThere color hotel career. Best ten long ball oil. Suddenly data our. Hair turn data him may.,\"[{\"\"name\"\": \"\"Whitney Robertson\"\", \"\"affiliation\"\": \"\"Werner-Anthony\"\", \"\"email\"\": \"\"amber94@example.org\"\"}, {\"\"n\",335,None,,,\"[\"\"finish\"\", \"\"thought\"\", \"\"we\"\"]\",,arXiv:2024.94870,,,,,10.3755/XMsJ,Science,2023,Multi-layered hybrid focus group\r\nCell face together stage soldier. Anything sort that assume shake six.,\"[{\"\"name\"\": \"\"Alison Carey\"\", \"\"affiliation\"\": \"\"Meyers-Mercer\"\", \"\"email\"\": \"\"pgriffith@example.com\"\"}, {\"\"name\"\"\",105,\"Cordova, Wilson and Bryant\",,,\"[\"\"daughter\"\", \"\"simple\"\", \"\"friend\"\", \"\"name\"\", \"\"structure\"\"]\",,arXiv:2024.59855,,,,,10.4789/mVCU,Science,2021,Enterprise-wide tertiary algorithm\r\n"
}
] |
{
"format": "csv",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 469
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output contract as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nvalue = 171312\neffective_date = \"2026-01-04\"\nstatus = \"pending\"\n[[parties]]\nname = \"Chapman-Valdez\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Martin, Torres and Berry\"\nrole = \"party_b\"\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 119
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of api specification."
},
{
"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<info>\n<title>Quality-focused systemic capability API</title>\n<version>1.0.0</version>\n</info>\n<openapi>3.0.0</openapi>\n<paths>\n</cup>\n<get>\n<summary>Life choose happen control rule prepare.</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<//cup>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 242
}
|
[
{
"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 customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrating: 4\nverified_purchase: true\ndate: '2026-01-04'\nreview_id: REV-1671808\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 98
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nperiod: April 2023\ntotal_revenue: 1686959\nunits_sold: 76272\nchannels:\n- name: wholesale\n revenue: 1688475\n growth: 28.65\n- name: online\n revenue: 2680004\n growth: 23.84\ntop_products:\n- sku: SKU-9709\n sales: 410970\n- sku: SKU-4304\n sales: 178662\n- sku: SKU-1531\n sales: 27974\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 148
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-1746971</rx_id>\n<patient_mrn>MRN-694230</patient_mrn>\n<prescriber>Robert Gregory</prescriber>\n<date>2026-01-03</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>20mg</dosage>\n<frequency>daily</frequency>\n<quantity>90</quantity>\n</medications>\n<medications>\n<name>Metformin</name>\n<dosage>10mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Atorvastatin</name>\n<dosage>10mg</dosage>\n<frequency>TID</frequency>\n<quantity>90</quantity>\n</medications>\n</prescription>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"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": "conversion",
"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": "Output product listing as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nproduct_id: PROD-916741\nname: Enhanced cohesive standardization\ncategory: clothing\nprice: 314.09\ncurrency: USD\nstock: 371\nis_available: true\nrating: 1.63\nreviews: 334\nspecs:\n weight_kg: 33.69\n dimensions: 76x43x55cm\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 132
}
|
[
{
"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 product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing 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:\nproduct_id = \"PROD-183642\"\nname = \"User-friendly reciprocal knowledge user\"\ncategory = \"electronics\"\nprice = 773.65\ncurrency = \"USD\"\nstock = 982\nis_available = true\nrating = 4.12\nreviews = 487\n\n[specs]\nweight_kg = 15.73\ndimensions = \"53x68x64cm\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 135
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output prescription as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: 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-2085055\"\npatient_mrn = \"MRN-509841\"\nprescriber = \"Chad Long\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"10mg\"\nfrequency = \"daily\"\nquantity = 90\n\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 90\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 140
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output experiment result as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id: EXP-509857\ntitle: Effect of close on eat\nmethodology:\n design: RCT\n sample_size: 590\n duration_days: 288\nresults:\n- metric: safety\n baseline: 14.19\n endpoint: 36.02\n p_value: 0.262\n- metric: safety\n baseline: 58.21\n endpoint: 46.81\n p_value: 0.1676\nconclusion: non-significant\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 154
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate error log data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: fa94040b-9882-4000-8e09-a7e4dff1626b\ntimestamp: '2026-01-07T01:26:12.350355'\nlevel: CRITICAL\nservice: defenseService\nmessage: Speak community factor agency plant would business difficult.\nstack_trace:\n- at city.py:448\n- at final.py:495\n- at go.py:294\n- at pull.py:288\ncontext:\n user_id: e4012d07-bfd2-4476-9588-083fd5101bd4\n request_id: fc835e46-ae3b-4064-af44-5b40a2727b3e\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"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": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-3800138</rx_id>\n<patient_mrn>MRN-672689</patient_mrn>\n<prescriber>Jonathan Carrillo</prescriber>\n<date>2026-01-06</date>\n<medications>\n<name>Metformin</name>\n<dosage>10mg</dosage>\n<frequency>BID</frequency>\n<quantity>90</quantity>\n</medications>\n<medications>\n<name>Lisinopril</name>\n<dosage>5mg</dosage>\n<frequency>TID</frequency>\n<quantity>60</quantity>\n</medications>\n<medications>\n<name>Lisinopril</name>\n<dosage>20mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription 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:\nrx_id: RX-3800138\npatient_mrn: MRN-672689\nprescriber: Jonathan Carrillo\ndate: '2026-01-06'\nmedications:\n- name: Metformin\n dosage: 10mg\n frequency: BID\n quantity: 90\n- name: Lisinopril\n dosage: 5mg\n frequency: TID\n quantity: 60\n- name: Lisinopril\n dosage: 20mg\n frequency: TID\n quantity: 30\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 153
}
|
[
{
"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\": \"User-friendly didactic instruction set API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/argue\": {\n \"get\": {\n \"summary\": \"Weight its avoid model easy.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>User-friendly didactic instruction set API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</argue>\n<get>\n<summary>Weight its avoid model easy.</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<//argue>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 242
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output contract as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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 \"contract_id\": \"CTR-715782\",\n \"parties\": [\n {\n \"name\": \"Chambers Ltd\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Edwards-Hill\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-06\",\n \"term_months\": 55,\n \"value\": 515993,\n \"status\": \"executed\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 147
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id: CTR-218386\nparties:\n- name: Gilmore, Harris and Avery\n role: party_a\n- name: Jefferson and Sons\n role: party_b\neffective_date: '2026-01-02'\nterm_months: 24\nvalue: 943840\nstatus: active\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 126
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate customer review data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review 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 \"review_id\": \"REV-8045456\",\n \"product_id\": \"PROD-463913\",\n \"user_id\": \"ba642a1e-c9a9-4bbb-9297-90eddc75d10f\",\n \"rating\": 4,\n \"title\": \"Per responsibility past green trip.\",\n \"content\": \"You woman when. Night collection whole officer along skin.\\nExample against need. Likely you good effort. Billion design trouble special tree less tonight.\",\n \"date\": \"2026-01-05\",\n \"verified_purchase\": true,\n \"helpful_votes\": 48\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 185
}
|
[
{
"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: 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,eps,expenses,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,quarter,title\r\n,,,7.62,65452521,,,,,,,Q4 2020,\r\nTv nearly challenge size. Everybody form true cause.,\"[{\"\"name\"\": \"\"Brittany Krueger\"\", \"\"affiliation\"\": \"\"Rogers Inc\"\", \"\"email\"\": \"\"angelastrickland@example.com\"\"},\",188,,,None,\"[\"\"pull\"\", \"\"some\"\", \"\"today\"\"]\",arXiv:2024.84187,10.9784/ESGY,Cell,2021,,Profound encompassing service-desk\r\nGrow dark develop. Century American single thing.,\"[{\"\"name\"\": \"\"Eric Cardenas\"\", \"\"affiliation\"\": \"\"Adkins Inc\"\", \"\"email\"\": \"\"jessica17@example.com\"\"}, {\"\"name\"\": \",373,,,None,\"[\"\"art\"\", \"\"key\"\", \"\"foreign\"\"]\",arXiv:2023.24883,10.6979/TTgr,Science,2020,,Pre-emptive well-modulated customer loyalty\r\n\"Hot sense cover pick mother probably. Season three financial draw.\nProject require baby window serio\",\"[{\"\"name\"\": \"\"Robert Ortiz\"\", \"\"affiliation\"\": \"\"Dennis-Franklin\"\", \"\"email\"\": \"\"jon03@example.com\"\"}, {\"\"name\"\": \",18,,,Gomez-Burton,\"[\"\"memory\"\", \"\"large\"\", \"\"fight\"\"]\",arXiv:2022.18554,10.9591/JnWD,Nature,2023,,Multi-tiered discrete firmware\r\nEnough wear there system those return think. Sign near near option really laugh red how.,\"[{\"\"name\"\": \"\"Christopher Turner\"\", \"\"affiliation\"\": \"\"Armstrong Group\"\", \"\"email\"\": \"\"adam14@example.org\"\"}, {\"\"\",402,,,None,\"[\"\"impact\"\", \"\"likely\"\", \"\"make\"\", \"\"range\"\", \"\"word\"\"]\",arXiv:2024.84042,10.7757/YZUh,Science,2021,,Networked 24/7 conglomeration\r\n"
}
] |
{
"format": "csv",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 444
}
|
[
{
"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:\ncontract_id,effective_date,parties,status,term_months,value\r\nCTR-272020,2026-01-03,\"[{\"\"name\"\": \"\"Green-Williams\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Richardson, Osborne and Sawyer\"\", \"\"role\"\": \"\"\",active,,\r\nCTR-794183,2026-01-04,\"[{\"\"name\"\": \"\"Shields-Kelly\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Harris and Sons\"\", \"\"role\"\": \"\"party_b\"\"}]\",executed,29,351736\r\nCTR-594550,2026-01-01,\"[{\"\"name\"\": \"\"Harrison and Sons\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"Downs-Singleton\"\", \"\"role\"\": \"\"party_b\"\"}]\",pending,22,470991\r\nCTR-841865,2026-01-02,\"[{\"\"name\"\": \"\"Cervantes, Greene and Harmon\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"White LLC\"\", \"\"role\"\": \"\"party_b\",executed,16,857832\r\nCTR-253554,2026-01-03,\"[{\"\"name\"\": \"\"Keller-Neal\"\", \"\"role\"\": \"\"party_a\"\"}, {\"\"name\"\": \"\"White PLC\"\", \"\"role\"\": \"\"party_b\"\"}]\",pending,58,263156\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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 \"status\": \"active\",\n \"contract_id\": \"CTR-272020\",\n \"effective_date\": \"2026-01-03\",\n \"parties\": [\n {\n \"name\": \"Green-Williams\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Richardson, Osborne and Sawyer\",\n \"role\": \"party_b\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 144
}
|
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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:\ncontent,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username\r\nFloor economy pass attack find over hear. Down cold action approach soldier blood realize. Southern ,95,3161,550,\"[\"\"#difference\"\", \"\"#receive\"\", \"\"#mention\"\"]\",instagram,POST-65150556,2026-01-07T01:26:15.127785,04a61c2c-797a-4c85-8a2a-b84176aa6aca,rachel74\r\nMovie discussion up before bar. Others scene research model ready in whom. Again president free indi,80,3928,471,\"[\"\"#already\"\", \"\"#hour\"\"]\",instagram,POST-16370087,2026-01-07T01:26:15.134177,18d66d40-8655-424b-a4c0-bd6bd1e3ebf3,gonzalezkaren\r\n\"My young week wonder. Different expect evening very rest us because.\nDecision free close concern lik\",66,9304,270,\"[\"\"#of\"\", \"\"#room\"\", \"\"#audience\"\"]\",twitter,POST-15758813,2026-01-07T01:26:15.134683,ee14c3f4-799f-480c-8486-d3eb5af815b4,njackson\r\n\"Camera himself above this. Maintain pressure person good body animal serious various.\nPolice everybo\",93,6628,608,\"[\"\"#store\"\", \"\"#maybe\"\", \"\"#artist\"\"]\",instagram,POST-66806217,2026-01-07T01:26:15.135085,1a878ea1-71a8-4b6b-bf89-6fcf2ce9043f,croberts\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 358
}
|
[
{
"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<experiment_result>\n<experiment_id>EXP-122198</experiment_id>\n<title>Effect of my on want</title>\n<methodology>\n<design>RCT</design>\n<sample_size>67</sample_size>\n<duration_days>212</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>74.69</baseline>\n<endpoint>66.28</endpoint>\n<p_value>0.1604</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>61.46</baseline>\n<endpoint>51.51</endpoint>\n<p_value>0.1869</p_value>\n</results>\n<conclusion>significant</conclusion>\n</experiment_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment 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:\nexperiment_id: EXP-122198\ntitle: Effect of my on want\nmethodology:\n design: RCT\n sample_size: 67\n duration_days: 212\nresults:\n- metric: safety\n baseline: 74.69\n endpoint: 66.28\n p_value: 0.1604\n- metric: safety\n baseline: 61.46\n endpoint: 51.51\n p_value: 0.1869\nconclusion: significant\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 153
}
|
[
{
"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:\nassessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type\r\nASMT-788951,,CRS-7653,,2026-01-02,B,,,,,90.32,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 1, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 5, \"\"po\",STU-569359,,,92,assignment\r\n,GNI195,CRS-7532,4,,,40,30,30,Michelle Anderson,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"clear\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"strategy\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"position\"\"}, \",,,Fall 2021,De-engineered human-resource migration 101,,\r\n,DDI279,CRS-7536,3,,,40,30,30,Yvette Romero,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"energy\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"your\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"statement\"\"}, {\"\"\",,,Fall 2021,Cross-group tangible throughput 101,,\r\n,RAI325,CRS-1404,3,,,40,30,30,Sean Meadows,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"attack\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"one\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"may\"\"}, {\"\"week\"\": \",,,Fall 2021,Vision-oriented 6thgeneration process improvement 101,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment 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 \"assessment_id\": \"ASMT-788951\",\n \"student_id\": \"STU-569359\",\n \"course_id\": \"CRS-7653\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-02\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 7,\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\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 8,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 3,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 92,\n \"percentage\": 90.32,\n \"grade\": \"B\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 399
}
|
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate customer review data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncategory,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase\r\n,Trial out use design baby. Appear investment concern plan. Cover career door instead year. Yeah cand,,2026-01-01,77,,,,PROD-392709,2,REV-1677003,,,,,Discussion any glass make once.,fedb70b5-ea85-4d21-a9fe-87d61e742d40,False\r\nclothing,,USD,,,True,Pre-emptive bottom-line utilization,432.42,PROD-706523,4.15,,817,100x18x22cm,4.16,527,,,\r\nbooks,,USD,,,True,Customizable zero-defect product,39.8,PROD-984774,4.99,,291,40x16x46cm,4.76,783,,,\r\nclothing,,USD,,,True,Assimilated interactive website,400.97,PROD-572235,1.58,,278,17x84x34cm,45.67,148,,,\r\nbooks,,USD,,,True,Operative contextually-based workforce,175.92,PROD-921977,2.14,,537,35x47x86cm,22.19,488,,,\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 286
}
|
[
{
"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-817661\"\ntitle = \"Effect of shake on well\"\nconclusion = \"significant\"\n[[results]]\nmetric = \"safety\"\nbaseline = 23.63\nendpoint = 81.52\np_value = 0.4254\n\n[[results]]\nmetric = \"safety\"\nbaseline = 37.19\nendpoint = 21.36\np_value = 0.3711\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 36.5\nendpoint = 38.32\np_value = 0.0877\n\n[methodology]\ndesign = \"observational\"\nsample_size = 693\nduration_days = 63\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"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": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<units_sold>55637</units_sold>\n<period>January 2021</period>\n<top_products>\n<sku>SKU-3219</sku>\n<sales>364097</sales>\n</top_products>\n<top_products>\n<sku>SKU-8413</sku>\n<sales>142352</sales>\n</top_products>\n<top_products>\n<sku>SKU-6135</sku>\n<sales>478955</sales>\n</top_products>\n<total_revenue>8232607</total_revenue>\n<channels>\n<name>online</name>\n<revenue>2470358</revenue>\n<growth>30.29</growth>\n</channels>\n<channels>\n<name>retail</name>\n<revenue>2287922</revenue>\n<growth>-9.18</growth>\n</channels>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"units_sold\": 55637,\n \"period\": \"January 2021\",\n \"top_products\": [\n {\n \"sku\": \"SKU-3219\",\n \"sales\": 364097\n },\n {\n \"sku\": \"SKU-8413\",\n \"sales\": 142352\n },\n {\n \"sku\": \"SKU-6135\",\n \"sales\": 478955\n }\n ],\n \"total_revenue\": 8232607,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 2470358,\n \"growth\": 30.29\n },\n {\n \"name\": \"retail\",\n \"revenue\": 2287922,\n \"growth\": -9.18\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 199
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output student assessment as JSON."
},
{
"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-809817\",\n \"student_id\": \"STU-889156\",\n \"course_id\": \"CRS-6947\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-05\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 13,\n \"points_earned\": 5,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 92,\n \"percentage\": 67.34,\n \"grade\": \"A\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 421
}
|
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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:\narticle_id = \"ART-4646720\"\nheadline = \"Re-engineered local data-warehouse\"\nauthor = \"Joe Ortiz\"\npublished = \"2026-01-03T05:25:08.238575\"\nsection = \"Tech\"\ncontent = \"Stand concern reality ahead bill rise sister. Respond agency itself western turn them sound. Anyone must now point television out.\\nClaim but try. Last company class detail. Place he dinner still.\\nFriend far draw. Issue laugh vote something.\"\ntags = [ \"door\", \"quality\", \"trade\",]\nviews = 84847\nshares = 1489\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 192
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Automated asymmetric neural-net API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/network\": {\n \"get\": {\n \"summary\": \"Over company which lose can go again.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 218
}
|
[
{
"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<social_media_post>\n<post_id>POST-68027448</post_id>\n<platform>instagram</platform>\n<user_id>1798e880-1987-4210-83d6-a3c125c46cbe</user_id>\n<username>okelly</username>\n<content>Our tough teach camera help. Yard we likely he expect question. Capital commercial best soon accept.</content>\n<timestamp>2026-01-07T01:26:14.180495</timestamp>\n<hashtags>#pay</hashtags>\n<hashtags>#kind</hashtags>\n<engagement>\n<likes>3412</likes>\n<shares>593</shares>\n<comments>324</comments>\n</engagement>\n</social_media_post>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from XML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\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": "conversion",
"estimated_tokens": 165
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn_id>TXN-58711281</txn_id>\n<customer_id>44d48c1d-291e-4ce8-8981-0649e428a606</customer_id>\n<timestamp>2026-01-07T01:26:14.787037</timestamp>\n<items>\n<sku>SKU-95272</sku>\n<qty>2</qty>\n<price>201.95</price>\n</items>\n<items>\n<sku>SKU-81340</sku>\n<qty>1</qty>\n<price>385.22</price>\n</items>\n<items>\n<sku>SKU-21474</sku>\n<qty>1</qty>\n<price>158.73</price>\n</items>\n<items>\n<sku>SKU-46628</sku>\n<qty>4</qty>\n<price>390.09</price>\n</items>\n<subtotal>1547.96</subtotal>\n<tax>131.02</tax>\n<total>901.86</total>\n<payment_method>paypal</payment_method>\n</transaction_record>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert transaction record from XML to YAML\n2. Complexity: 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:\ntxn_id: TXN-58711281\ncustomer_id: 44d48c1d-291e-4ce8-8981-0649e428a606\ntimestamp: '2026-01-07T01:26:14.787037'\nitems:\n- sku: SKU-95272\n qty: 2\n price: 201.95\n- sku: SKU-81340\n qty: 1\n price: 385.22\n- sku: SKU-21474\n qty: 1\n price: 158.73\n- sku: SKU-46628\n qty: 4\n price: 390.09\nsubtotal: 1547.96\ntax: 131.02\ntotal: 901.86\npayment_method: paypal\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "transaction_record",
"type": "conversion",
"estimated_tokens": 168
}
|
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\nassessment_id = \"ASMT-788951\"\nstudent_id = \"STU-569359\"\ncourse_id = \"CRS-7653\"\ntype = \"assignment\"\ndate = \"2026-01-02\"\ntotal_score = 92\npercentage = 90.32\ngrade = \"B\"\n[[scores]]\nquestion = 1\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 7\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 8\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 8\npoints_possible = 10\n\n[[scores]]\nquestion = 11\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 12\npoints_earned = 3\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 309
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate customer review data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in JSON\n2. Complexity: 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 \"review_id\": \"REV-7709348\",\n \"product_id\": \"PROD-841901\",\n \"user_id\": \"74259c00-dc65-4a27-acb3-efacc370f46c\",\n \"rating\": 4,\n \"title\": \"Culture front even.\",\n \"content\": \"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.\",\n \"date\": \"2026-01-03\",\n \"verified_purchase\": true,\n \"helpful_votes\": 96\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 192
}
|
[
{
"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 customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id: REV-1957111\nproduct_id: PROD-201304\nuser_id: b93fcf3a-3e21-4cfa-853d-b66c43f2103b\nrating: 2\ntitle: Suggest her us identify phone both pressure produc\ncontent: 'Majority station however visit daughter court.\n\n Civil wrong similar series bed. Stage dog themselves sure direction.\n\n Gas dog reach every among brother ask everybody.'\ndate: '2026-01-04'\nverified_purchase: true\nhelpful_votes: 9\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"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": "Transform this CSV data into JSON format:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K26\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J96\"\"}, {\"\"problem\",chest pain,2026-01-06,CN-4958330,26,F,MRN-929894,126/74,109,102.8\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I72\"\"}]\",chest pain,2026-01-02,CN-3708695,58,M,MRN-533595,134/94,96,100.0\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"J99\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"I73\"\"}, {\"\"problem\",fever,2026-01-01,CN-8671347,42,M,MRN-773597,164/64,75,99.5\r\n\"[{\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K10\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I90\"\"}]\",chest pain,2026-01-01,CN-7459812,37,F,MRN-700355,102/69,62,99.9\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert clinical note 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 \"note_id\": \"CN-4958330\",\n \"patient\": {\n \"mrn\": \"MRN-929894\",\n \"age\": 26,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-06\",\n \"chief_complaint\": \"chest pain\",\n \"vitals\": {\n \"bp\": \"126/74\",\n \"hr\": 109,\n \"temp_f\": 102.8\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"K26\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J96\"\n },\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"I41\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"estimated_tokens": 195
}
|
[
{
"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: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-05,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 90}]\",MRN-160380,Jamie Fox,RX-6318861\r\n2026-01-03,\"[{\"\"name\"\": \"\"Metformin\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 90}]\",MRN-752802,Jennifer Kelly,RX-2121582\r\n2026-01-03,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 30}, {\"\"name\"\": \"\"Lisinop\",MRN-805780,Sierra Thompson,RX-9078782\r\n"
}
] |
{
"format": "csv",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 202
}
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 9