warheads/qwen3-4b-structured-output-lora-14
Text Generation • Updated
• 15
Datasets:
messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output structured data for product_listing using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "toml",
"complexity": "simple",
"schema": "product_listing",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for product_listing using TOML.",
"output": "Approach:\n1. Define the schema: The product_listing should contain a dictionary with 3 root fields (product, price, stock) and a nesting depth of 1.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nproduct = \"interesting\"\nprice = 96.01\nstock = 50\n",
"estimated_tokens": 147
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate minified YAML for clinical_note (no whitespace)."
},
{
"role": "assistant",
"content": "Approach:\n1. Defin... | {
"format": "yaml",
"complexity": "complex",
"schema": "clinical_note",
"constraint": "minified",
"type": "generation",
"prompt": "Generate minified YAML for clinical_note (no whitespace).",
"output": "Approach:\n1. Define the schema: The clinical_note should contain a dictionary with 6 root fields (id, patient, diagnosis...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens. Output must be minified (no extra whitespace/newlines).\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary and compress output.\n\nOutput:\nid: 34521865-f6c3-4e7d-b484-cb106211928f\npatient: Jordan Conrad\ndiagnosis: feeling\nnotes: Skill prepare according cold wind light. About value professional reveal need.\n Improve professor social control.\nmeta_info:\n generated_at: '2026-01-23T05:23:24.492928'\n version: v5.0\n tags:\n - human\n - happy\n - result\n - friend\n - deal\naudit_log:\n- action: created\n by: ericcasey\n timestamp: '1995-01-14T22:49:24.681452'\n",
"estimated_tokens": 262
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<items>\n<sku>SKU-89816</sku>\n<... | {
"format": "json",
"complexity": "simple",
"schema": "transaction_record",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 156
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\nid,patient,diagnosis,notes\r\nfa33fc7a-5622-4429-8cb0-56326bae20d6,Sandra Clayton,perform,Be... | {
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following CSV to JSON:\nid,patient,diagnosis,notes\r\nfa33fc7a-5622-4429-8cb0-56326bae20d6,Sandra Clayton,perform,Behind international whether remember you student far. Check student according themselves. Public same these ten enter law.\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 4 root fields (id, patient, diagnosis...) and a nesting depth of 1.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"id\": \"fa33fc7a-5622-4429-8cb0-56326bae20d6\",\n \"patient\": \"Sandra Clayton\",\n \"diagnosis\": \"perform\",\n \"notes\": \"Behind international whether remember you student far. Check student according themselves. Public same these ten enter law.\"\n}",
"estimated_tokens": 205
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output lab result as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in CSV\n2. Complexity... | {
"format": "csv",
"complexity": "complex",
"schema": "lab_result",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 251
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate course syllabus data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"constraint": null,
"type": "generation",
"prompt": "Generate course syllabus data in XML format.",
"output": "Approach:\n1. Define the schema: The course_syllabus should contain a dictionary with 3 root fields (course, weeks, credits) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course>Mandatory foreground implementation</course>\n<weeks>12</weeks>\n<credits>3</credits>\n</course_syllabus>",
"estimated_tokens": 180
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the CSV below into JSON:\nperiod,sales,region,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nQ1,3... | {
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"constraint": null,
"type": "conversion",
"prompt": "Reformat the CSV below into JSON:\nperiod,sales,region,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nQ1,3534,Port Stevenberg,2026-01-22T04:03:06.907803,v2.0,\"[\"\"whatever\"\", \"\"some\"\", \"\"condition\"\", \"\"bring\"\", \"\"reach\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"shellybernard\"\", \"\"timestamp\"\": \"\"2011-03-18T20:56:07.916810\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"kevingray\"\", \"\"timestamp\"\": \"\"2019-01-11T01:40:57.976149\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"pjohnson\"\", \"\"timestamp\"\": \"\"1975-11-01T16:18:55.743514\"\"}]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 5 root fields (period, sales, region...) and a nesting depth of 3.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"period\": \"Q1\",\n \"sales\": 3534,\n \"region\": \"Port Stevenberg\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:06.907803\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"whatever\",\n \"some\",\n \"condition\",\n \"bring\",\n \"reach\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"shellybernard\",\n \"timestamp\": \"2011-03-18T20:56:07.916810\"\n },\n {\n \"action\": \"created\",\n \"by\": \"kevingray\",\n \"timestamp\": \"2019-01-11T01:40:57.976149\"\n },\n {\n \"action\": \"created\",\n \"by\": \"pjohnson\",\n \"timestamp\": \"1975-11-01T16:18:55.743514\"\n }\n ]\n}",
"estimated_tokens": 300
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output news_article data in XML, ensuring all keys are sorted."
},
{
"role": "assistant",
"content": "Approach:\n1. De... | {
"format": "xml",
"complexity": "complex",
"schema": "news_article",
"constraint": "sorted",
"type": "generation",
"prompt": "Output news_article data in XML, ensuring all keys are sorted.",
"output": "Approach:\n1. Define the schema: The news_article should contain a dictionary with 5 root fields (headline, body, author...) and a nesting depth of 3.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags. Keys must be sorted alphabetically.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>He plant professor surface sense.</headline>\n<body>Sound dream local discover store writer bank situation. Quickly theory north surface oil nothing some. Late reflect movement set sound itself different.</body>\n<author>Phillip Erickson</author>\n<meta_info>\n<generated_at>2026-01-23T05:23:23.981268</generated_at>\n<version>v3.0</version>\n<tags>people</tags>\n<tags>economic</tags>\n<tags>opportunity</tags>\n<tags>nature</tags>\n<tags>bit</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>turnerryan</by>\n<timestamp>2011-07-22T00:20:05.157000</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>ronaldwhite</by>\n<timestamp>1986-08-22T10:42:26.856129</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>ecoleman</by>\n<timestamp>1988-09-23T17:25:59.936787</timestamp>\n</audit_log>\n</news_article>",
"estimated_tokens": 370
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate financial report data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial re... | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML... | {
"format": "toml",
"complexity": "simple",
"schema": "contract",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 117
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of random structured data."
},
{
"role": "assistant",
"content": "Approach:\n1. Define ... | {
"format": "yaml",
"complexity": "simple",
"schema": "random_structured_data",
"constraint": null,
"type": "generation",
"prompt": "Create a YAML representation of random structured data.",
"output": "Approach:\n1. Define the schema: The random_structured_data should contain a dictionary with 1 root fields (random_content) and a nesting depth of 1.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nrandom_content: themselves\n",
"estimated_tokens": 144
} |
[
{
"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 \"reviews\": 730,\n \"category\": \"books\",\n \"stock\": 824,\n \"is_available\": true,\n ... | {
"format": "xml",
"complexity": "simple",
"schema": "product_listing",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 144
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate research paper data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research pa... | {
"format": "yaml",
"complexity": "medium",
"schema": "research_paper",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 220
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn>1d18bb9e-9d98-498c-8d... | {
"format": "json",
"complexity": "medium",
"schema": "transaction_record",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<transaction_record>\n<txn>1d18bb9e-9d98-498c-8d68-b0e54a9d47d0</txn>\n<amount>358.44</amount>\n<status>completed</status>\n</transaction_record>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (txn, amount, status) and a nesting depth of 1.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"txn\": \"1d18bb9e-9d98-498c-8d68-b0e54a9d47d0\",\n \"amount\": 358.44,\n \"status\": \"completed\"\n}",
"estimated_tokens": 166
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YA... | {
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 166
} |
[
{
"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... | {
"format": "yaml",
"complexity": "simple",
"schema": "prescription",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 109
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"company\": \"Richard Ltd\",\n \"ticker\": \"XHCL\",\n \"quarter\": \"Q4 2020\",\n \... | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 164
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"product_id\": \"PROD-891981\",\n \"name\": \"Focused background info-mediaries\",\n ... | {
"format": "xml",
"complexity": "complex",
"schema": "product_listing",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 182
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output structured data for api_specification using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define... | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for api_specification using TOML.",
"output": "Approach:\n1. Define the schema: The api_specification should contain a dictionary with 5 root fields (endpoint, method, responses...) and a nesting depth of 3.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nendpoint = \"/api/v1/users\"\nmethod = \"GET\"\n[[audit_log]]\naction = \"created\"\nby = \"kimberlyjones\"\ntimestamp = \"2026-01-16T13:36:50.885954\"\n\n[responses]\n200 = \"OK\"\n\n[meta_info]\ngenerated_at = \"2026-01-23T05:23:25.273743\"\nversion = \"v4.0\"\ntags = [ \"next\", \"box\", \"some\", \"resource\", \"relationship\",]\n",
"estimated_tokens": 211
} |
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial... | {
"format": "xml",
"complexity": "medium",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output structured data for student_assessment using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "xml",
"complexity": "complex",
"schema": "student_assessment",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for student_assessment using XML.",
"output": "Approach:\n1. Define the schema: The student_assessment should contain a dictionary with 5 root fields (student, score, grade...) and a nesting depth of 3.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Scott Avery</student>\n<score>31</score>\n<grade>C</grade>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.179661</generated_at>\n<version>v2.0</version>\n<tags>data</tags>\n<tags>sort</tags>\n<tags>world</tags>\n<tags>notice</tags>\n<tags>foot</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>angie36</by>\n<timestamp>2002-01-29T16:21:09.968726</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>myersdustin</by>\n<timestamp>1983-06-28T20:59:32.361167</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>michaelking</by>\n<timestamp>2019-04-24T00:16:41.731738</timestamp>\n</audit_log>\n</student_assessment>",
"estimated_tokens": 315
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output structured data for random_structured_data using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. D... | {
"format": "toml",
"complexity": "medium",
"schema": "random_structured_data",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for random_structured_data using TOML.",
"output": "Approach:\n1. Define the schema: The random_structured_data should contain a dictionary with 1 root fields (random_content) and a nesting depth of 1.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nrandom_content = \"among\"\n",
"estimated_tokens": 141
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate prescription data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"constraint": null,
"type": "generation",
"prompt": "Generate prescription data in XML format.",
"output": "Approach:\n1. Define the schema: The prescription should contain a dictionary with 3 root fields (rx, drug, dosage) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx>94dfbb11-504d-4ec3-9bdf-3c04d75f2822</rx>\n<drug>push</drug>\n<dosage>10mg</dosage>\n</prescription>",
"estimated_tokens": 175
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"constraint": null,
"type": "generation",
"prompt": "Create a JSON representation of product listing.",
"output": "Approach:\n1. Define the schema: The product_listing should contain a dictionary with 3 root fields (product, price, stock) and a nesting depth of 1.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"product\": \"back\",\n \"price\": 95.89,\n \"stock\": 13\n}",
"estimated_tokens": 151
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate research paper data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research pa... | {
"format": "toml",
"complexity": "complex",
"schema": "research_paper",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 207
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output structured data for news_article using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "json",
"complexity": "medium",
"schema": "news_article",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for news_article using JSON.",
"output": "Approach:\n1. Define the schema: The news_article should contain a dictionary with 3 root fields (headline, body, author) and a nesting depth of 1.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"headline\": \"Me guy movie personal.\",\n \"body\": \"Forward accept glass week traditional save. Ready effect politics standard local court.\\nEnd realize someone near discuss summer address. Play next produce throw. List Mr evidence thousand.\",\n \"author\": \"John Gibson\"\n}",
"estimated_tokens": 204
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research... | {
"format": "toml",
"complexity": "simple",
"schema": "research_paper",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 163
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<article_id>ART-8846154</article_id>\n... | {
"format": "json",
"complexity": "complex",
"schema": "news_article",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 221
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this data from TOML to YAML:\nstudent = \"Destiny Dixon\"\nscore = 5\ngrade = \"A\"\n"
},
{
"role": "assistant... | {
"format": "yaml",
"complexity": "medium",
"schema": "student_assessment",
"constraint": null,
"type": "conversion",
"prompt": "Transform this data from TOML to YAML:\nstudent = \"Destiny Dixon\"\nscore = 5\ngrade = \"A\"\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (student, score, grade) and a nesting depth of 1.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nstudent: Destiny Dixon\nscore: 5\ngrade: A\n",
"estimated_tokens": 153
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial r... | {
"format": "csv",
"complexity": "medium",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 201
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in ... | {
"format": "json",
"complexity": "medium",
"schema": "error_log",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 186
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Create a JSON representation of experiment result.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"experiment_id\": \"EXP-744915\",\n \"title\": \"Analysis of budget\",\n \"metrics\": {\n \"accuracy\": 0.8186,\n \"loss\": 0.275,\n \"epoch\": 96\n },\n \"config\": {\n \"batch_size\": 128,\n \"optimizer\": \"sgd\",\n \"lr\": 0.001\n }\n}",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following CSV to TOML:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp... | {
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 144
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Transform this data from JSON to TOML:\n{\n \"experiment_id\": \"EXP-764444\",\n \"title\": \"Analysis of land\",\n \"metrics... | {
"format": "toml",
"complexity": "complex",
"schema": "experiment_result",
"constraint": null,
"type": "conversion",
"prompt": "Transform this data from JSON to TOML:\n{\n \"experiment_id\": \"EXP-764444\",\n \"title\": \"Analysis of land\",\n \"metrics\": {\n \"accuracy\": 0.8143,\n \"loss\": 0.311,\n \"epoch\": 78\n },\n \"config\": {\n \"batch_size\": 32,\n \"optimizer\": \"adam\",\n \"lr\": 0.001\n },\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.459141\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"pattern\",\n \"wide\",\n \"at\",\n \"step\",\n \"ahead\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"harrisjoseph\",\n \"timestamp\": \"1973-04-29T08:04:24.792312\"\n },\n {\n \"action\": \"created\",\n \"by\": \"uwalsh\",\n \"timestamp\": \"1978-03-29T09:36:00.148631\"\n },\n {\n \"action\": \"created\",\n \"by\": \"aramirez\",\n \"timestamp\": \"2024-06-26T06:47:17.411040\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 6 root fields (experiment_id, title, metrics...) and a nesting depth of 3.\n2. Identify the target format requirements: TOML requires strict syntax. Define hierarchy using dot-notation or [section] headers.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nexperiment_id = \"EXP-764444\"\ntitle = \"Analysis of land\"\n[[audit_log]]\naction = \"created\"\nby = \"harrisjoseph\"\ntimestamp = \"1973-04-29T08:04:24.792312\"\n\n[[audit_log]]\naction = \"created\"\nby = \"uwalsh\"\ntimestamp = \"1978-03-29T09:36:00.148631\"\n\n[[audit_log]]\naction = \"created\"\nby = \"aramirez\"\ntimestamp = \"2024-06-26T06:47:17.411040\"\n\n[metrics]\naccuracy = 0.8143\nloss = 0.311\nepoch = 78\n\n[config]\nbatch_size = 32\noptimizer = \"adam\"\nlr = 0.001\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.459141\"\nversion = \"v2.0\"\ntags = [ \"pattern\", \"wide\", \"at\", \"step\", \"ahead\",]\n",
"estimated_tokens": 285
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the YAML below into TOML:\nid: 152a2f45-19bf-49ba-8f05-a0fc97da6a2d\npatient: Candice Jensen\ndiagnosis: very\nnotes: P... | {
"format": "toml",
"complexity": "complex",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": "Reformat the YAML below into TOML:\nid: 152a2f45-19bf-49ba-8f05-a0fc97da6a2d\npatient: Candice Jensen\ndiagnosis: very\nnotes: Pass control sign popular manager. Play form scientist not focus manager. Area\n last history identify responsibility front.\nmeta_info:\n generated_at: '2026-01-22T04:03:06.396103'\n version: v3.0\n tags:\n - future\n - read\n - any\n - individual\n - record\naudit_log:\n- action: created\n by: charles61\n timestamp: '1986-01-10T09:12:59.093491'\n- action: created\n by: jennifer27\n timestamp: '2021-08-26T19:04:41.813805'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 6 root fields (id, patient, diagnosis...) and a nesting depth of 3.\n2. Identify the target format requirements: TOML requires strict syntax. Define hierarchy using dot-notation or [section] headers.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nid = \"152a2f45-19bf-49ba-8f05-a0fc97da6a2d\"\npatient = \"Candice Jensen\"\ndiagnosis = \"very\"\nnotes = \"Pass control sign popular manager. Play form scientist not focus manager. Area last history identify responsibility front.\"\n[[audit_log]]\naction = \"created\"\nby = \"charles61\"\ntimestamp = \"1986-01-10T09:12:59.093491\"\n\n[[audit_log]]\naction = \"created\"\nby = \"jennifer27\"\ntimestamp = \"2021-08-26T19:04:41.813805\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.396103\"\nversion = \"v3.0\"\ntags = [ \"future\", \"read\", \"any\", \"individual\", \"record\",]\n",
"estimated_tokens": 277
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.opt... | {
"format": "yaml",
"complexity": "medium",
"schema": "experiment_result",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following CSV to YAML:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr\r\nEXP-977053,Analysis of no,0.864,0.221,32,64,adam,0.001\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nexperiment_id: EXP-977053\ntitle: Analysis of no\nmetrics:\n accuracy: 0.864\n loss: 0.221\n epoch: 32\nconfig:\n batch_size: 64\n optimizer: adam\n lr: 0.001\n",
"estimated_tokens": 185
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate social media post data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social m... | {
"format": "json",
"complexity": "medium",
"schema": "social_media_post",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 190
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate api specification data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": "Generate api specification data in TOML format.",
"output": "Approach:\n1. Define the schema: The api_specification should contain a dictionary with 5 root fields (endpoint, method, responses...) and a nesting depth of 3.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nendpoint = \"/api/v1/users\"\nmethod = \"GET\"\n[[audit_log]]\naction = \"created\"\nby = \"cynthiamiranda\"\ntimestamp = \"2001-08-25T07:17:07.336188\"\n\n[responses]\n200 = \"OK\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.386413\"\nversion = \"v3.0\"\ntags = [ \"space\", \"possible\", \"recognize\", \"four\", \"change\",]\n",
"estimated_tokens": 212
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output experiment result as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in T... | {
"format": "toml",
"complexity": "complex",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate experiment result data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Generate experiment result data in XML format.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-481272</experiment_id>\n<title>Analysis of production</title>\n<metrics>\n<accuracy>0.9889</accuracy>\n<loss>0.3569</loss>\n<epoch>46</epoch>\n</metrics>\n<config>\n<batch_size>128</batch_size>\n<optimizer>adam</optimizer>\n<lr>0.001</lr>\n</config>\n</experiment_result>",
"estimated_tokens": 225
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output api specification as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in T... | {
"format": "toml",
"complexity": "simple",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 188
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output financial report as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in JSO... | {
"format": "json",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 138
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate financial report data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schem... | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": "Generate financial report data in YAML format.",
"output": "Approach:\n1. Define the schema: The financial_report should contain a dictionary with 5 root fields (company, revenue, profit...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ncompany: Knight-Myers\nrevenue: 965087\nprofit: 5261\nmeta_info:\n generated_at: '2026-01-23T05:23:24.425493'\n version: v2.0\n tags:\n - near\n - toward\n - number\n - term\n - after\naudit_log:\n- action: created\n by: ashley23\n timestamp: '2010-07-16T11:18:37.276251'\n- action: created\n by: michael96\n timestamp: '1985-04-20T21:02:30.787193'\n",
"estimated_tokens": 225
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following YAML to JSON:\ncourse: Customer-focused heuristic toolset\nweeks: 12\ncredits: 3\nmeta_info:\n generated_... | {
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following YAML to JSON:\ncourse: Customer-focused heuristic toolset\nweeks: 12\ncredits: 3\nmeta_info:\n generated_at: '2026-01-22T04:03:07.050026'\n version: v3.0\n tags:\n - cut\n - result\n - campaign\n - network\n - make\naudit_log:\n- action: created\n by: rochamichael\n timestamp: '2011-03-20T22:35:12.834387'\n- action: created\n by: pray\n timestamp: '2021-05-21T15:12:16.651042'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (course, weeks, credits...) and a nesting depth of 3.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"course\": \"Customer-focused heuristic toolset\",\n \"weeks\": 12,\n \"credits\": 3,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:07.050026\",\n \"version\": \"v3.0\",\n \"tags\": [\n \"cut\",\n \"result\",\n \"campaign\",\n \"network\",\n \"make\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"rochamichael\",\n \"timestamp\": \"2011-03-20T22:35:12.834387\"\n },\n {\n \"action\": \"created\",\n \"by\": \"pray\",\n \"timestamp\": \"2021-05-21T15:12:16.651042\"\n }\n ]\n}",
"estimated_tokens": 274
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output transaction record as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in... | {
"format": "toml",
"complexity": "complex",
"schema": "transaction_record",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 148
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the YAML below into TOML:\nid: d0dc0493-a2d0-46bc-9272-eb001bac4f6d\npatient: Julia Williams\ndiagnosis: pay\nnotes: 'W... | {
"format": "toml",
"complexity": "simple",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": "Reformat the YAML below into TOML:\nid: d0dc0493-a2d0-46bc-9272-eb001bac4f6d\npatient: Julia Williams\ndiagnosis: pay\nnotes: 'Wish write experience ever happen program family.\n\n Subject result head run message poor. Attack wind close Mr thousand wall. Must population\n evening far provide old share.'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 4 root fields (id, patient, diagnosis...) and a nesting depth of 1.\n2. Identify the target format requirements: TOML requires strict syntax. Define hierarchy using dot-notation or [section] headers.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nid = \"d0dc0493-a2d0-46bc-9272-eb001bac4f6d\"\npatient = \"Julia Williams\"\ndiagnosis = \"pay\"\nnotes = \"Wish write experience ever happen program family.\\nSubject result head run message poor. Attack wind close Mr thousand wall. Must population evening far provide old share.\"\n",
"estimated_tokens": 209
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following CSV to XML:\nperiod,sales,region\r\nQ1,1528,Jonathanfort\r\n"
},
{
"role": "assistant",
"content... | {
"format": "xml",
"complexity": "simple",
"schema": "sales_analytics",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nperiod,sales,region\r\nQ1,1528,Jonathanfort\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (period, sales, region) and a nesting depth of 1.\n2. Identify the target format requirements: XML requires strict syntax. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>Q1</period>\n<sales>1528</sales>\n<region>Jonathanfort</region>\n</sales_analytics>",
"estimated_tokens": 180
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output student assessment as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in CS... | {
"format": "csv",
"complexity": "complex",
"schema": "student_assessment",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 280
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output structured data for experiment_result using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define th... | {
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for experiment_result using XML.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-880755</experiment_id>\n<title>Analysis of project</title>\n<metrics>\n<accuracy>0.7685</accuracy>\n<loss>0.4944</loss>\n<epoch>84</epoch>\n</metrics>\n<config>\n<batch_size>64</batch_size>\n<optimizer>adam</optimizer>\n<lr>0.001</lr>\n</config>\n</experiment_result>",
"estimated_tokens": 224
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate api specification data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specifi... | {
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 228
} |
[
{
"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<customer_review>\n<review_id>REV-2691236</revi... | {
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 181
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output structured data for experiment_result using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define... | {
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for experiment_result using YAML.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 6 root fields (experiment_id, title, metrics...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nexperiment_id: EXP-106352\ntitle: Analysis of be\nmetrics:\n accuracy: 0.8381\n loss: 0.2299\n epoch: 72\nconfig:\n batch_size: 64\n optimizer: adam\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:06.706806'\n version: v3.0\n tags:\n - newspaper\n - country\n - instead\n - chair\n - hospital\naudit_log:\n- action: created\n by: robertweber\n timestamp: '2023-06-21T13:37:30.380115'\n",
"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": "Produce a XML document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student a... | {
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 438
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course sylla... | {
"format": "csv",
"complexity": "complex",
"schema": "course_syllabus",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 375
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note ... | {
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 180
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social ... | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 194
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "json",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": "Create a JSON representation of api specification.",
"output": "Approach:\n1. Define the schema: The api_specification should contain a dictionary with 5 root fields (endpoint, method, responses...) and a nesting depth of 3.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"endpoint\": \"/api/v1/users\",\n \"method\": \"GET\",\n \"responses\": {\n \"200\": \"OK\"\n },\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.009064\",\n \"version\": \"v3.0\",\n \"tags\": [\n \"describe\",\n \"economic\",\n \"protect\",\n \"on\",\n \"through\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"rodriguezjohnny\",\n \"timestamp\": \"1994-10-26T05:01:25.608282\"\n },\n {\n \"action\": \"created\",\n \"by\": \"victoriaadams\",\n \"timestamp\": \"1991-01-11T08:18:19.412188\"\n },\n {\n \"action\": \"created\",\n \"by\": \"daniel45\",\n \"timestamp\": \"1977-11-02T00:39:57.766938\"\n }\n ]\n}",
"estimated_tokens": 303
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-986141</product_id... | {
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 149
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"review_id\": \"REV-2691236\",\n \"product_id\": \"PROD-245093\",\n \"user_id\": \"98b0ec97-... | {
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 211
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output financial report as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in XML\n2... | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output structured data for prescription using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "json",
"complexity": "complex",
"schema": "prescription",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for prescription using JSON.",
"output": "Approach:\n1. Define the schema: The prescription should contain a dictionary with 5 root fields (rx, drug, dosage...) and a nesting depth of 3.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"rx\": \"1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1\",\n \"drug\": \"me\",\n \"dosage\": \"10mg\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.190126\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"suddenly\",\n \"those\",\n \"experience\",\n \"each\",\n \"seem\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"lewisapril\",\n \"timestamp\": \"1990-03-27T18:23:16.981344\"\n },\n {\n \"action\": \"created\",\n \"by\": \"hjohnson\",\n \"timestamp\": \"1990-08-17T03:08:04.190155\"\n }\n ]\n}",
"estimated_tokens": 268
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment... | {
"format": "csv",
"complexity": "medium",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 331
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "xml",
"complexity": "medium",
"schema": "sales_analytics",
"constraint": null,
"type": "generation",
"prompt": "Create a XML representation of sales analytics.",
"output": "Approach:\n1. Define the schema: The sales_analytics should contain a dictionary with 3 root fields (period, sales, region) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>Q1</period>\n<sales>1399</sales>\n<region>Sandraberg</region>\n</sales_analytics>",
"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 XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<service>approachService</service>... | {
"format": "json",
"complexity": "simple",
"schema": "error_log",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 168
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate TOML for api_specification with keys sorted alphabetically."
},
{
"role": "assistant",
"content": "Approach... | {
"format": "toml",
"complexity": "medium",
"schema": "api_specification",
"constraint": "sorted",
"type": "generation",
"prompt": "Generate TOML for api_specification with keys sorted alphabetically.",
"output": "Approach:\n1. Define the schema: The api_specification should contain a dictionary with 3 root fields (endpoint, method, responses) and a nesting depth of 2.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers. Keys must be sorted alphabetically.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nendpoint = \"/api/v1/users\"\nmethod = \"GET\"\n\n[responses]\n200 = \"OK\"\n",
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this data from CSV to YAML:\ntimestamp,level,message\r\n2026-01-22T04:03:06.143016,ERROR,My condition happy enjoy hear... | {
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"constraint": null,
"type": "conversion",
"prompt": "Transform this data from CSV to YAML:\ntimestamp,level,message\r\n2026-01-22T04:03:06.143016,ERROR,My condition happy enjoy hear.\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (timestamp, level, message) and a nesting depth of 1.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\ntimestamp: '2026-01-22T04:03:06.143016'\nlevel: ERROR\nmessage: My condition happy enjoy hear.\n",
"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 error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in ... | {
"format": "json",
"complexity": "medium",
"schema": "error_log",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output error log as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in CSV\n2. Complexity: ... | {
"format": "csv",
"complexity": "complex",
"schema": "error_log",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 477
} |
[
{
"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 \"txn_id\": \"TXN-59995807\",\n \"customer_id\": \"0d66cadd-c42f-4e9b-ae40-46d71f47623d... | {
"format": "xml",
"complexity": "complex",
"schema": "transaction_record",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 218
} |
[
{
"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\": \"Streamlined logistical help-des... | {
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 246
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<assessment>\n<problem>diabete... | {
"format": "json",
"complexity": "simple",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 154
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert to YAML with sorted keys:\n{\n \"id\": \"de8037f4-ba9d-43eb-b737-866288f76046\",\n \"test\": \"billion\",\n \"value\"... | {
"format": "yaml",
"complexity": "simple",
"schema": "lab_result",
"constraint": "sorted",
"type": "conversion",
"prompt": "Convert to YAML with sorted keys:\n{\n \"id\": \"de8037f4-ba9d-43eb-b737-866288f76046\",\n \"test\": \"billion\",\n \"value\": 55.7053151709492\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (id, test, value) and a nesting depth of 1.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens. Keys must be sorted alphabetically.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema and applying constraints.\n\nOutput:\nid: de8037f4-ba9d-43eb-b737-866288f76046\ntest: billion\nvalue: 55.7053151709492\n",
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate customer review data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "yaml",
"complexity": "complex",
"schema": "customer_review",
"constraint": null,
"type": "generation",
"prompt": "Generate customer review data in YAML format.",
"output": "Approach:\n1. Define the schema: The customer_review should contain a dictionary with 5 root fields (user, rating, comment...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nuser: jeffersonjames\nrating: 4\ncomment: Medical myself however weight admit for likely say.\nmeta_info:\n generated_at: '2026-01-22T04:03:05.096294'\n version: v1.0\n tags:\n - note\n - police\n - offer\n - sing\n - friend\naudit_log:\n- action: created\n by: jenniferbartlett\n timestamp: '2023-09-11T15:31:12.547088'\n- action: created\n by: ahoward\n timestamp: '1992-07-11T20:06:55.844429'\n",
"estimated_tokens": 235
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate news article data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "xml",
"complexity": "medium",
"schema": "news_article",
"constraint": null,
"type": "generation",
"prompt": "Generate news article data in XML format.",
"output": "Approach:\n1. Define the schema: The news_article should contain a dictionary with 3 root fields (headline, body, author) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Become there think west wear wear.</headline>\n<body>One task machine. Want professional bar issue. Four plant responsibility.\nOne rich strategy. Gun Republican child. Year discussion land order respond entire peace.</body>\n<author>Monica Wagner</author>\n</news_article>",
"estimated_tokens": 221
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate news article data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "json",
"complexity": "complex",
"schema": "news_article",
"constraint": null,
"type": "generation",
"prompt": "Generate news article data in JSON format.",
"output": "Approach:\n1. Define the schema: The news_article should contain a dictionary with 5 root fields (headline, body, author...) and a nesting depth of 3.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"headline\": \"Read usually realize line body.\",\n \"body\": \"Identify bring point week. Stock hit along PM memory force.\\nNext state your investment success. Agreement we nice start we similar.\",\n \"author\": \"Adam Williams\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.898106\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"record\",\n \"try\",\n \"security\",\n \"must\",\n \"else\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"uhenderson\",\n \"timestamp\": \"2019-02-01T09:49:00.564726\"\n }\n ]\n}",
"estimated_tokens": 275
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate contract data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The c... | {
"format": "yaml",
"complexity": "simple",
"schema": "contract",
"constraint": null,
"type": "generation",
"prompt": "Generate contract data in YAML format.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ncontract: deploy integrated ROI\nparties:\n- Nelson-Hamilton\n- Jackson-Burton\nsigned: true\n",
"estimated_tokens": 159
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "toml",
"complexity": "medium",
"schema": "transaction_record",
"constraint": null,
"type": "generation",
"prompt": "Create a TOML representation of transaction record.",
"output": "Approach:\n1. Define the schema: The transaction_record should contain a dictionary with 3 root fields (txn, amount, status) and a nesting depth of 1.\n2. Select the format: TOML is chosen. Define hierarchy using dot-notation or [section] headers.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ntxn = \"260f9831-29af-467a-8739-aabd00406e01\"\namount = 483.09\nstatus = \"completed\"\n",
"estimated_tokens": 155
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output structured data for contract using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "csv",
"complexity": "medium",
"schema": "contract",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for contract using CSV.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: CSV is chosen. Flatten the hierarchical structure. Use dot notation for nested keys in the header.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ncontract,parties,signed\r\nstrategize 24/7 platforms,\"[\"\"Brown Inc\"\", \"\"Park Ltd\"\"]\",False\r\n",
"estimated_tokens": 163
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api spe... | {
"format": "yaml",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 196
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output structured data for random_structured_data using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. D... | {
"format": "json",
"complexity": "medium",
"schema": "random_structured_data",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for random_structured_data using JSON.",
"output": "Approach:\n1. Define the schema: The random_structured_data should contain a dictionary with 1 root fields (random_content) and a nesting depth of 1.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"random_content\": \"picture\"\n}",
"estimated_tokens": 145
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output structured data for experiment_result using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define... | {
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for experiment_result using YAML.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 6 root fields (experiment_id, title, metrics...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nexperiment_id: EXP-332585\ntitle: Analysis of for\nmetrics:\n accuracy: 0.8382\n loss: 0.3964\n epoch: 89\nconfig:\n batch_size: 32\n optimizer: sgd\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:07.415527'\n version: v2.0\n tags:\n - western\n - response\n - glass\n - parent\n - adult\naudit_log:\n- action: created\n by: hrogers\n timestamp: '1975-01-23T05:52:05.213977'\n",
"estimated_tokens": 235
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following JSON to YAML:\n{\n \"timestamp\": \"2026-01-22T04:03:06.848557\",\n \"level\": \"ERROR\",\n \"message\"... | {
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following JSON to YAML:\n{\n \"timestamp\": \"2026-01-22T04:03:06.848557\",\n \"level\": \"ERROR\",\n \"message\": \"Condition talk down.\"\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (timestamp, level, message) and a nesting depth of 1.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\ntimestamp: '2026-01-22T04:03:06.848557'\nlevel: ERROR\nmessage: Condition talk down.\n",
"estimated_tokens": 165
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news artic... | {
"format": "yaml",
"complexity": "medium",
"schema": "news_article",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 199
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate customer review data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"constraint": null,
"type": "generation",
"prompt": "Generate customer review data in JSON format.",
"output": "Approach:\n1. Define the schema: The customer_review should contain a dictionary with 5 root fields (user, rating, comment...) and a nesting depth of 3.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"user\": \"ortizdaniel\",\n \"rating\": 4,\n \"comment\": \"Get south particular voice learn option him.\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-23T05:23:23.557993\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"medical\",\n \"human\",\n \"whose\",\n \"behavior\",\n \"play\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"kmendoza\",\n \"timestamp\": \"2001-08-07T08:54:03.593431\"\n }\n ]\n}",
"estimated_tokens": 245
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.opt... | {
"format": "json",
"complexity": "medium",
"schema": "experiment_result",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following CSV to JSON:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr\r\nEXP-977053,Analysis of no,0.864,0.221,32,64,adam,0.001\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"experiment_id\": \"EXP-977053\",\n \"title\": \"Analysis of no\",\n \"metrics\": {\n \"accuracy\": 0.864,\n \"loss\": 0.221,\n \"epoch\": 32\n },\n \"config\": {\n \"batch_size\": 64,\n \"optimizer\": \"adam\",\n \"lr\": 0.001\n }\n}",
"estimated_tokens": 201
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<financial_report>\n<company>Martinez, Patterso... | {
"format": "json",
"complexity": "complex",
"schema": "financial_report",
"constraint": null,
"type": "conversion",
"prompt": null,
"output": null,
"estimated_tokens": 140
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create tran... | {
"format": "toml",
"complexity": "medium",
"schema": "transaction_record",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 136
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following TOML to YAML:\ntimestamp = \"2026-01-22T04:03:05.390145\"\nlevel = \"ERROR\"\nmessage = \"Thus gun listen ... | {
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following TOML to YAML:\ntimestamp = \"2026-01-22T04:03:05.390145\"\nlevel = \"ERROR\"\nmessage = \"Thus gun listen close.\"\n[[audit_log]]\naction = \"created\"\nby = \"ywolf\"\ntimestamp = \"2000-02-19T05:35:31.909361\"\n\n[[audit_log]]\naction = \"created\"\nby = \"monica03\"\ntimestamp = \"1980-04-27T09:58:15.554391\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.390376\"\nversion = \"v4.0\"\ntags = [ \"fill\", \"summer\", \"gun\", \"discussion\", \"end\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (timestamp, level, message...) and a nesting depth of 3.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\ntimestamp: '2026-01-22T04:03:05.390145'\nlevel: ERROR\nmessage: Thus gun listen close.\nmeta_info:\n generated_at: '2026-01-22T04:03:05.390376'\n version: v4.0\n tags:\n - fill\n - summer\n - gun\n - discussion\n - end\naudit_log:\n- action: created\n by: ywolf\n timestamp: '2000-02-19T05:35:31.909361'\n- action: created\n by: monica03\n timestamp: '1980-04-27T09:58:15.554391'\n",
"estimated_tokens": 238
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Transform this data from YAML to CSV:\nid: f75c09a7-2bda-4c77-b916-21c422f10848\npatient: Emily Mcdonald\ndiagnosis: in\nnotes: 'F... | {
"format": "csv",
"complexity": "medium",
"schema": "clinical_note",
"constraint": null,
"type": "conversion",
"prompt": "Transform this data from YAML to CSV:\nid: f75c09a7-2bda-4c77-b916-21c422f10848\npatient: Emily Mcdonald\ndiagnosis: in\nnotes: 'Fill just never must see bad. Through bring result film thus small.\n\n Inside along line hospital. Wind behind item room early west.'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 4 root fields (id, patient, diagnosis...) and a nesting depth of 1.\n2. Identify the target format requirements: CSV requires strict syntax. Flatten the hierarchical structure. Use dot notation for nested keys in the header.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nid,patient,diagnosis,notes\r\nf75c09a7-2bda-4c77-b916-21c422f10848,Emily Mcdonald,in,\"Fill just never must see bad. Through bring result film thus small.\nInside along line hospital. Wind behind item room early west.\"\r\n",
"estimated_tokens": 202
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api spe... | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 205
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output structured data for experiment_result using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define... | {
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for experiment_result using YAML.",
"output": "Approach:\n1. Define the schema: The experiment_result should contain a dictionary with 6 root fields (experiment_id, title, metrics...) and a nesting depth of 3.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\nexperiment_id: EXP-616884\ntitle: Analysis of and\nmetrics:\n accuracy: 0.7673\n loss: 0.4367\n epoch: 22\nconfig:\n batch_size: 32\n optimizer: sgd\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:05.730891'\n version: v4.0\n tags:\n - suddenly\n - western\n - well\n - ahead\n - director\naudit_log:\n- action: created\n by: thomasmarvin\n timestamp: '2007-02-20T21:53:12.454337'\n",
"estimated_tokens": 237
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in ... | {
"format": "yaml",
"complexity": "simple",
"schema": "lab_result",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 204
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this data from TOML to YAML:\nuser = \"rcrawford\"\nrating = 5\ncomment = \"Actually fill art opportunity magazine.\"\... | {
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"constraint": null,
"type": "conversion",
"prompt": "Transform this data from TOML to YAML:\nuser = \"rcrawford\"\nrating = 5\ncomment = \"Actually fill art opportunity magazine.\"\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (user, rating, comment) and a nesting depth of 1.\n2. Identify the target format requirements: YAML requires strict syntax. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nuser: rcrawford\nrating: 5\ncomment: Actually fill art opportunity magazine.\n",
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate transaction record data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "csv",
"complexity": "complex",
"schema": "transaction_record",
"constraint": null,
"type": "generation",
"prompt": "Generate transaction record data in CSV format.",
"output": "Approach:\n1. Define the schema: The transaction_record should contain a dictionary with 5 root fields (txn, amount, status...) and a nesting depth of 3.\n2. Select the format: CSV is chosen. Flatten the hierarchical structure. Use dot notation for nested keys in the header.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ntxn,amount,status,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n57c23f62-6431-4d9b-92e3-6afc44ca62ff,64.37,completed,2026-01-23T05:23:24.908789,v4.0,\"[\"\"same\"\", \"\"white\"\", \"\"man\"\", \"\"interview\"\", \"\"play\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"maysjeremy\"\", \"\"timestamp\"\": \"\"1985-07-02T17:58:15.002367\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"judyhenry\"\", \"\"timestamp\"\": \"\"1998-03-10T21:47:41.928864\"\"}]\"\r\n",
"estimated_tokens": 249
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output structured data for random_structured_data using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Defi... | {
"format": "xml",
"complexity": "complex",
"schema": "random_structured_data",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for random_structured_data using XML.",
"output": "Approach:\n1. Define the schema: The random_structured_data should contain a dictionary with 3 root fields (random_content, meta_info, audit_log) and a nesting depth of 3.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<random_structured_data>\n<random_content>\n<relate>True</relate>\n<early_1>such</early_1>\n</random_content>\n<random_content>\n<of>False</of>\n<part_1>False</part_1>\n</random_content>\n<random_content>game</random_content>\n<meta_info>\n<generated_at>2026-01-23T05:23:25.010040</generated_at>\n<version>v2.0</version>\n<tags>physical</tags>\n<tags>choice</tags>\n<tags>pick</tags>\n<tags>southern</tags>\n<tags>knowledge</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>wrightheather</by>\n<timestamp>1991-10-03T16:34:17.131264</timestamp>\n</audit_log>\n</random_structured_data>",
"estimated_tokens": 297
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create studen... | {
"format": "json",
"complexity": "simple",
"schema": "student_assessment",
"constraint": null,
"type": "generation",
"prompt": null,
"output": null,
"estimated_tokens": 99
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert to JSON with sorted keys:\nauthor: April Swanson\nbody: 'Operation writer dinner upon. Employee lay system seven once.\n... | {
"format": "json",
"complexity": "medium",
"schema": "news_article",
"constraint": "sorted",
"type": "conversion",
"prompt": "Convert to JSON with sorted keys:\nauthor: April Swanson\nbody: 'Operation writer dinner upon. Employee lay system seven once.\n\n Wife wall song treatment offer job. Game analysis number daughter other parent reason.\n Leg write book system family owner management.'\nheadline: Focus middle actually no forget cultural kind.\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 3 root fields (headline, body, author) and a nesting depth of 1.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces. Keys must be sorted alphabetically.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema and applying constraints.\n\nOutput:\n{\n \"author\": \"April Swanson\",\n \"body\": \"Operation writer dinner upon. Employee lay system seven once.\\nWife wall song treatment offer job. Game analysis number daughter other parent reason. Leg write book system family owner management.\",\n \"headline\": \"Focus middle actually no forget cultural kind.\"\n}",
"estimated_tokens": 235
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following CSV to XML:\nrandom_content\r\n\"[{\"\"only\"\": [[\"\"environmental\"\", \"\"speak\"\", null, 4.17], [\"\"t... | {
"format": "xml",
"complexity": "medium",
"schema": "random_structured_data",
"constraint": null,
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nrandom_content\r\n\"[{\"\"only\"\": [[\"\"environmental\"\", \"\"speak\"\", null, 4.17], [\"\"tax\"\", 4.95, true, \"\"adult\"\"], [73, 84, 8.25, false, false], [\"\"big\"\", false, null, null]]}, \"\"positive\"\"]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 1 root fields (random_content) and a nesting depth of 5.\n2. Identify the target format requirements: XML requires strict syntax. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<random_structured_data>\n<random_content>\n<only>['environmental', 'speak', None, 4.17]</only>\n<only>['tax', 4.95, True, 'adult']</only>\n<only>[73, 84, 8.25, False, False]</only>\n<only>['big', False, None, None]</only>\n</random_content>\n<random_content>positive</random_content>\n</random_structured_data>",
"estimated_tokens": 227
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output structured data for contract using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "yaml",
"complexity": "simple",
"schema": "contract",
"constraint": null,
"type": "generation",
"prompt": "Output structured data for contract using YAML.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ncontract: strategize turn-key deliverables\nparties:\n- Daugherty-Hayes\n- Bonilla, Price and Baker\nsigned: true\n",
"estimated_tokens": 164
} |
End of preview. Expand
in Data Studio
This is the concatenated datasets of
- u-10bei/structured_data_with_cot_dataset_512_v2 (train 5000 records)
- u-10bei/structured_data_with_cot_dataset_512_v4 (train 3000 records)
- u-10bei/structured_data_with_cot_dataset_512_v5 (train 2000 records)
with sampling.
- Downloads last month
- 6
Size of downloaded dataset files:
5.34 MB
Size of the auto-converted Parquet files:
5.34 MB
Number of rows:
10,000