messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "csv",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"prompt": "Create a CSV representation of product listing.",
"output": "Approach:\n1. Define the schema: The product_listing should contain a dictionary with 5 root fields (product, price, stock...) 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:\nproduct,price,stock,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nthough,98.15,48,2026-01-22T04:03:06.289897,v3.0,\"[\"\"blood\"\", \"\"each\"\", \"\"guy\"\", \"\"knowledge\"\", \"\"two\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"james40\"\", \"\"timestamp\"\": \"\"1991-01-22T23:28:56.955736\"\"}]\"\r\n",
"estimated_tokens": 214
} |
[
{
"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:\nheadline,body,author\r\nReally style television analysis.,\"Pm reflect role build. Do ground pa... | {
"format": "xml",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nheadline,body,author\r\nReally style television analysis.,\"Pm reflect role build. Do ground participant film build data religious.\nFree station why and. Fill life threat lead assume serious assume. Remain return above visit.\",Jose Garcia\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (headline, body, author) 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<news_article>\n<headline>Really style television analysis.</headline>\n<body>Pm reflect role build. Do ground participant film build data religious.\nFree station why and. Fill life threat lead assume serious assume. Remain return above visit.</body>\n<author>Jose Garcia</author>\n</news_article>",
"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": "Transform this data from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>Q1</period>\n<sale... | {
"format": "yaml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"prompt": "Transform this data from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>Q1</period>\n<sales>1573</sales>\n<region>Dunnview</region>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.297151</generated_at>\n<version>v5.0</version>\n<tags>real</tags>\n<tags>word</tags>\n<tags>show</tags>\n<tags>land</tags>\n<tags>over</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>michael49</by>\n<timestamp>2014-08-19T12:53:38.260481</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>david08</by>\n<timestamp>1992-08-27T05:51:20.774593</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>john53</by>\n<timestamp>2022-06-25T13:06:39.665068</timestamp>\n</audit_log>\n</sales_analytics>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (period, sales, region...) 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:\nperiod: Q1\nsales: 1573\nregion: Dunnview\nmeta_info:\n generated_at: '2026-01-22T04:03:07.297151'\n version: v5.0\n tags:\n - real\n - word\n - show\n - land\n - over\naudit_log:\n- action: created\n by: michael49\n timestamp: '2014-08-19T12:53:38.260481'\n- action: created\n by: david08\n timestamp: '1992-08-27T05:51:20.774593'\n- action: created\n by: john53\n timestamp: '2022-06-25T13:06:39.665068'\n",
"estimated_tokens": 243
} |
[
{
"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 prescription using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"prompt": "Output structured data for prescription using TOML.",
"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: 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:\nrx = \"0a25dfe7-54d1-4268-8410-2cf64bf21278\"\ndrug = \"machine\"\ndosage = \"10mg\"\n",
"estimated_tokens": 152
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following CSV to TOML:\nrx,drug,dosage,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n1a8dfd53... | {
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"prompt": "Convert the following CSV to TOML:\nrx,drug,dosage,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1,me,10mg,2026-01-22T04:03:05.190126,v1.0,\"[\"\"suddenly\"\", \"\"those\"\", \"\"experience\"\", \"\"each\"\", \"\"seem\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"lewisapril\"\", \"\"timestamp\"\": \"\"1990-03-27T18:23:16.981344\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"hjohnson\"\", \"\"timestamp\"\": \"\"1990-08-17T03:08:04.190155\"\"}]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 5 root fields (rx, drug, dosage...) 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:\nrx = \"1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1\"\ndrug = \"me\"\ndosage = \"10mg\"\n[[audit_log]]\naction = \"created\"\nby = \"lewisapril\"\ntimestamp = \"1990-03-27T18:23:16.981344\"\n\n[[audit_log]]\naction = \"created\"\nby = \"hjohnson\"\ntimestamp = \"1990-08-17T03:08:04.190155\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.190126\"\nversion = \"v1.0\"\ntags = [ \"suddenly\", \"those\", \"experience\", \"each\", \"seem\",]\n",
"estimated_tokens": 237
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate lab result data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"prompt": "Generate lab result data in TOML format.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 5 root fields (id, test, value...) 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:\nid = \"c540bd9d-4cd8-44b3-8173-3113630fa509\"\ntest = \"tonight\"\nvalue = 82.54530668576918\n[[audit_log]]\naction = \"created\"\nby = \"ahaas\"\ntimestamp = \"1974-06-20T11:00:56.029330\"\n\n[[audit_log]]\naction = \"created\"\nby = \"hawkinschase\"\ntimestamp = \"2003-04-28T17:29:53.203663\"\n\n[[audit_log]]\naction = \"created\"\nby = \"nrobinson\"\ntimestamp = \"2007-05-30T05:22:00.342399\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.041771\"\nversion = \"v3.0\"\ntags = [ \"catch\", \"animal\", \"federal\", \"gun\", \"task\",]\n",
"estimated_tokens": 255
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the YAML below into CSV:\nid: 62ce2508-53cc-4b4a-875e-cec49ce83d33\ntest: these\nvalue: 34.11560568209377\nmeta_info:\n ... | {
"format": "csv",
"complexity": "complex",
"schema": "lab_result",
"type": "conversion",
"prompt": "Reformat the YAML below into CSV:\nid: 62ce2508-53cc-4b4a-875e-cec49ce83d33\ntest: these\nvalue: 34.11560568209377\nmeta_info:\n generated_at: '2026-01-22T04:03:05.076453'\n version: v1.0\n tags:\n - focus\n - learn\n - necessary\n - show\n - tough\naudit_log:\n- action: created\n by: robertorivera\n timestamp: '1996-10-20T14:13:13.684689'\n- action: created\n by: iwalker\n timestamp: '1992-11-23T07:09:44.600586'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (id, test, value...) and a nesting depth of 3.\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,test,value,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n62ce2508-53cc-4b4a-875e-cec49ce83d33,these,34.11560568209377,2026-01-22T04:03:05.076453,v1.0,\"[\"\"focus\"\", \"\"learn\"\", \"\"necessary\"\", \"\"show\"\", \"\"tough\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"robertorivera\"\", \"\"timestamp\"\": \"\"1996-10-20T14:13:13.684689\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"iwalker\"\", \"\"timestamp\"\": \"\"1992-11-23T07:09:44.600586\"\"}]\"\r\n",
"estimated_tokens": 255
} |
[
{
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "yaml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"prompt": "Create a YAML representation of course syllabus.",
"output": "Approach:\n1. Define the schema: The course_syllabus should contain a dictionary with 5 root fields (course, weeks, credits...) 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:\ncourse: Organized systematic Graphical User Interface\nweeks: 12\ncredits: 3\nmeta_info:\n generated_at: '2026-01-22T04:03:06.528060'\n version: v3.0\n tags:\n - sound\n - traditional\n - yard\n - think\n - population\naudit_log:\n- action: created\n by: csantiago\n timestamp: '2013-12-23T12:17:29.826978'\n",
"estimated_tokens": 214
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following YAML to TOML:\ntxn: 6e1f092f-d57b-4a36-842d-93e63cba9405\namount: 425.58\nstatus: completed\nmeta_info:\n ... | {
"format": "toml",
"complexity": "complex",
"schema": "transaction_record",
"type": "conversion",
"prompt": "Convert the following YAML to TOML:\ntxn: 6e1f092f-d57b-4a36-842d-93e63cba9405\namount: 425.58\nstatus: completed\nmeta_info:\n generated_at: '2026-01-22T04:03:05.106739'\n version: v3.0\n tags:\n - take\n - under\n - subject\n - compare\n - lawyer\naudit_log:\n- action: created\n by: youngamanda\n timestamp: '2016-04-18T16:32:04.400302'\n- action: created\n by: amckee\n timestamp: '1986-08-27T00:14:30.888935'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (txn, amount, status...) 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:\ntxn = \"6e1f092f-d57b-4a36-842d-93e63cba9405\"\namount = 425.58\nstatus = \"completed\"\n[[audit_log]]\naction = \"created\"\nby = \"youngamanda\"\ntimestamp = \"2016-04-18T16:32:04.400302\"\n\n[[audit_log]]\naction = \"created\"\nby = \"amckee\"\ntimestamp = \"1986-08-27T00:14:30.888935\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.106739\"\nversion = \"v3.0\"\ntags = [ \"take\", \"under\", \"subject\", \"compare\", \"lawyer\",]\n",
"estimated_tokens": 240
} |
[
{
"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",
"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-802887</experiment_id>\n<title>Analysis of especially</title>\n<metrics>\n<accuracy>0.7219</accuracy>\n<loss>0.4423</loss>\n<epoch>59</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": 225
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate error log data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"prompt": "Generate error log data in YAML format.",
"output": "Approach:\n1. Define the schema: The error_log should contain a dictionary with 3 root fields (timestamp, level, message) 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:\ntimestamp: '2026-01-22T04:03:06.821685'\nlevel: ERROR\nmessage: Follow perform image fight end drop.\n",
"estimated_tokens": 161
} |
[
{
"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.330874\",\n \"level\": \"ERROR\",\n \"message\"... | {
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"prompt": "Convert the following JSON to YAML:\n{\n \"timestamp\": \"2026-01-22T04:03:06.330874\",\n \"level\": \"ERROR\",\n \"message\": \"Option body foot table truth group.\"\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.330874'\nlevel: ERROR\nmessage: Option body foot table truth group.\n",
"estimated_tokens": 169
} |
[
{
"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 product_listing using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"prompt": "Output structured data for product_listing using JSON.",
"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\": \"PM\",\n \"price\": 94.95,\n \"stock\": 43\n}",
"estimated_tokens": 150
} |
[
{
"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:\nuser,post,likes\r\ntommyshelton,\"Hear traditional mother recent pressure. Collection big light... | {
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nuser,post,likes\r\ntommyshelton,\"Hear traditional mother recent pressure. Collection big light nothing memory these sport.\nParent dream political stop.\",124\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (user, post, likes) 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<social_media_post>\n<user>tommyshelton</user>\n<post>Hear traditional mother recent pressure. Collection big light nothing memory these sport.\nParent dream political stop.</post>\n<likes>124</likes>\n</social_media_post>",
"estimated_tokens": 207
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate social media post data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"prompt": "Generate social media post data in YAML format.",
"output": "Approach:\n1. Define the schema: The social_media_post should contain a dictionary with 5 root fields (user, post, likes...) 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: robin72\npost: Ball moment really less. Walk want laugh management produce lose. Themselves\n shake measure create last focus.\nlikes: 239\nmeta_info:\n generated_at: '2026-01-22T04:03:05.086673'\n version: v5.0\n tags:\n - couple\n - film\n - gun\n - build\n - pull\naudit_log:\n- action: created\n by: sean67\n timestamp: '2009-04-02T11:37:07.729349'\n- action: created\n by: pearsonsarah\n timestamp: '1995-08-13T15:47:45.614852'\n",
"estimated_tokens": 246
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the CSV below into TOML:\nproduct,price,stock\r\nstudy,17.84,15\r\n"
},
{
"role": "assistant",
"content": "... | {
"format": "toml",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"prompt": "Reformat the CSV below into TOML:\nproduct,price,stock\r\nstudy,17.84,15\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (product, price, stock) 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:\nproduct = \"study\"\nprice = 17.84\nstock = 15\n",
"estimated_tokens": 151
} |
[
{
"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 XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Desiree Webb</... | {
"format": "toml",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"prompt": "Transform this data from XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Desiree Webb</student>\n<score>89</score>\n<grade>B</grade>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.623983</generated_at>\n<version>v5.0</version>\n<tags>sell</tags>\n<tags>population</tags>\n<tags>deal</tags>\n<tags>activity</tags>\n<tags>describe</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>alexanderharris</by>\n<timestamp>2013-07-19T10:19:23.859232</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>mark65</by>\n<timestamp>2021-04-26T06:15:44.085474</timestamp>\n</audit_log>\n</student_assessment>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (student, score, grade...) 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:\nstudent = \"Desiree Webb\"\nscore = 89\ngrade = \"B\"\n[[audit_log]]\naction = \"created\"\nby = \"alexanderharris\"\ntimestamp = \"2013-07-19T10:19:23.859232\"\n\n[[audit_log]]\naction = \"created\"\nby = \"mark65\"\ntimestamp = \"2021-04-26T06:15:44.085474\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.623983\"\nversion = \"v5.0\"\ntags = [ \"sell\", \"population\", \"deal\", \"activity\", \"describe\",]\n",
"estimated_tokens": 234
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the JSON below into XML:\n{\n \"rx\": \"7d4b6095-90a3-4ea8-8a9d-ff58756d8ff5\",\n \"drug\": \"energy\",\n \"dosage\": ... | {
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"prompt": "Reformat the JSON below into XML:\n{\n \"rx\": \"7d4b6095-90a3-4ea8-8a9d-ff58756d8ff5\",\n \"drug\": \"energy\",\n \"dosage\": \"10mg\"\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (rx, drug, dosage) 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<prescription>\n<rx>7d4b6095-90a3-4ea8-8a9d-ff58756d8ff5</rx>\n<drug>energy</drug>\n<dosage>10mg</dosage>\n</prescription>",
"estimated_tokens": 182
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "xml",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"prompt": "Create a XML representation of api specification.",
"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: 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<api_specification>\n<endpoint>/api/v1/users</endpoint>\n<method>GET</method>\n<responses>\n<_200>OK</_200>\n</responses>\n</api_specification>",
"estimated_tokens": 184
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "csv",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"prompt": "Create a CSV representation of experiment result.",
"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: 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:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nEXP-750115,Analysis of art,0.8804,0.4258,67,64,adam,0.001,2026-01-22T04:03:06.457781,v2.0,\"[\"\"agree\"\", \"\"small\"\", \"\"tax\"\", \"\"participant\"\", \"\"lose\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"chadfowler\"\", \"\"timestamp\"\": \"\"2001-12-16T07:09:33.116073\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"amandaprice\"\", \"\"timestamp\"\": \"\"2025-03-14T03:49:51.874209\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"susanmeyers\"\", \"\"timestamp\"\": \"\"1973-07-26T23:46:43.783834\"\"}]\"\r\n",
"estimated_tokens": 301
} |
[
{
"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:\nstudent,score,grade\r\nLaura Hall,93,A\r\n"
},
{
"role": "assistant",
"content": "A... | {
"format": "xml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nstudent,score,grade\r\nLaura Hall,93,A\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (student, score, grade) 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<student_assessment>\n<student>Laura Hall</student>\n<score>93</score>\n<grade>A</grade>\n</student_assessment>",
"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": "Convert the following TOML to JSON:\nproduct = \"why\"\nprice = 49.26\nstock = 4\n"
},
{
"role": "assistant",
"conte... | {
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"prompt": "Convert the following TOML to JSON:\nproduct = \"why\"\nprice = 49.26\nstock = 4\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (product, price, stock) 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 \"product\": \"why\",\n \"price\": 49.26,\n \"stock\": 4\n}",
"estimated_tokens": 156
} |
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "xml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"prompt": "Create a XML representation of news article.",
"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.\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>Authority life front box.</headline>\n<body>Resource scientist threat very better teacher. Better call small large network test writer. Above until still little simply it store. Course suffer paper yourself.</body>\n<author>Daniel Ortega</author>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.530524</generated_at>\n<version>v3.0</version>\n<tags>network</tags>\n<tags>individual</tags>\n<tags>increase</tags>\n<tags>table</tags>\n<tags>already</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>jessica58</by>\n<timestamp>2019-01-13T14:48:48.490407</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>stoneerika</by>\n<timestamp>2021-06-13T01:47:46.883065</timestamp>\n</audit_log>\n</news_article>",
"estimated_tokens": 332
} |
[
{
"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 CSV to TOML:\nuser,rating,comment\r\nmcbridedennis,4,Now through hospital one.\r\n"
},
{
"role"... | {
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"prompt": "Transform this data from CSV to TOML:\nuser,rating,comment\r\nmcbridedennis,4,Now through hospital one.\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (user, rating, comment) 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:\nuser = \"mcbridedennis\"\nrating = 4\ncomment = \"Now through hospital one.\"\n",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schem... | {
"format": "csv",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"prompt": "Create a CSV representation of financial report.",
"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: 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:\ncompany,revenue,profit,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nOlson Group,415401,26016,2026-01-22T04:03:05.121653,v4.0,\"[\"\"bit\"\", \"\"site\"\", \"\"camera\"\", \"\"stage\"\", \"\"subject\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jerry98\"\", \"\"timestamp\"\": \"\"1999-05-13T13:25:44.981805\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"matthewstephens\"\", \"\"timestamp\"\": \"\"2005-07-31T21:21:14.636113\"\"}]\"\r\n",
"estimated_tokens": 244
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the JSON below into YAML:\n{\n \"headline\": \"Behavior yet ask difficult PM.\",\n \"body\": \"Though staff head work... | {
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"prompt": "Reformat the JSON below into YAML:\n{\n \"headline\": \"Behavior yet ask difficult PM.\",\n \"body\": \"Though staff head worker other call. Campaign call alone carry former. Live teach fast never be woman available.\",\n \"author\": \"Karen Bennett\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.321791\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"budget\",\n \"it\",\n \"sea\",\n \"sit\",\n \"woman\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"wardkaitlyn\",\n \"timestamp\": \"2022-10-07T13:11:05.072118\"\n },\n {\n \"action\": \"created\",\n \"by\": \"eparsons\",\n \"timestamp\": \"2011-07-09T12:56:15.657947\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (headline, body, author...) 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:\nheadline: Behavior yet ask difficult PM.\nbody: Though staff head worker other call. Campaign call alone carry former. Live\n teach fast never be woman available.\nauthor: Karen Bennett\nmeta_info:\n generated_at: '2026-01-22T04:03:05.321791'\n version: v2.0\n tags:\n - budget\n - it\n - sea\n - sit\n - woman\naudit_log:\n- action: created\n by: wardkaitlyn\n timestamp: '2022-10-07T13:11:05.072118'\n- action: created\n by: eparsons\n timestamp: '2011-07-09T12:56:15.657947'\n",
"estimated_tokens": 262
} |
[
{
"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": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Generate customer review data in YAML format.",
"output": "Approach:\n1. Define the schema: The customer_review should contain a dictionary with 3 root fields (user, rating, comment) 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:\nuser: kimberlyruiz\nrating: 1\ncomment: Real along likely check cut chair.\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": "Generate transaction record data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "csv",
"complexity": "complex",
"schema": "transaction_record",
"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\na2a21367-3995-4fc1-9134-9127b3dce120,370.83,completed,2026-01-22T04:03:07.201416,v4.0,\"[\"\"major\"\", \"\"about\"\", \"\"yourself\"\", \"\"would\"\", \"\"maintain\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"ernestjacobs\"\", \"\"timestamp\"\": \"\"1974-08-10T15:07:17.873548\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"bharmon\"\", \"\"timestamp\"\": \"\"1983-06-17T10:13:31.692769\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"madisonwashington\"\", \"\"timestamp\"\": \"\"1985-08-19T18:37:31.167179\"\"}]\"\r\n",
"estimated_tokens": 277
} |
[
{
"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 transaction_record using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"prompt": "Output structured data for transaction_record using XML.",
"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: 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<transaction_record>\n<txn>3ed32e60-9522-4eaf-9732-08552512ba97</txn>\n<amount>246.17</amount>\n<status>completed</status>\n</transaction_record>",
"estimated_tokens": 183
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate prescription data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "json",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"prompt": "Generate prescription data in JSON 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: 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\": \"ed4b285e-adf9-499d-ab76-d7a7e8402da3\",\n \"drug\": \"ask\",\n \"dosage\": \"10mg\"\n}",
"estimated_tokens": 157
} |
[
{
"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": "complex",
"schema": "experiment_result",
"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,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nEXP-804895,Analysis of year,0.7691,0.473,50,32,adam,0.001,2026-01-22T04:03:06.038438,v4.0,\"[\"\"machine\"\", \"\"employee\"\", \"\"certainly\"\", \"\"plan\"\", \"\"official\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jasonferguson\"\", \"\"timestamp\"\": \"\"1989-09-28T18:41:06.715987\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"georgekrista\"\", \"\"timestamp\"\": \"\"2012-10-29T22:34:19.270194\"\"}]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV 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: 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-804895\ntitle: Analysis of year\nmetrics:\n accuracy: 0.7691\n loss: 0.473\n epoch: 50\nconfig:\n batch_size: 32\n optimizer: adam\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:06.038438'\n version: v4.0\n tags:\n - machine\n - employee\n - certainly\n - plan\n - official\naudit_log:\n- action: created\n by: jasonferguson\n timestamp: '1989-09-28T18:41:06.715987'\n- action: created\n by: georgekrista\n timestamp: '2012-10-29T22:34:19.270194'\n",
"estimated_tokens": 263
} |
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"prompt": "Create a TOML representation of social media post.",
"output": "Approach:\n1. Define the schema: The social_media_post should contain a dictionary with 3 root fields (user, post, likes) 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:\nuser = \"tommyshelton\"\npost = \"Hear traditional mother recent pressure. Collection big light nothing memory these sport.\\nParent dream political stop.\"\nlikes = 124\n",
"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": "Output structured data for experiment_result using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define... | {
"format": "json",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"prompt": "Output structured data for experiment_result using JSON.",
"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: 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-616884\",\n \"title\": \"Analysis of and\",\n \"metrics\": {\n \"accuracy\": 0.7673,\n \"loss\": 0.4367,\n \"epoch\": 22\n },\n \"config\": {\n \"batch_size\": 32,\n \"optimizer\": \"sgd\",\n \"lr\": 0.001\n },\n \"meta_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\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"thomasmarvin\",\n \"timestamp\": \"2007-02-20T21:53:12.454337\"\n }\n ]\n}",
"estimated_tokens": 280
} |
[
{
"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 XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<timestamp>2026-01-22T04:03:04.9... | {
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"prompt": "Transform this data from XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<timestamp>2026-01-22T04:03:04.968084</timestamp>\n<level>ERROR</level>\n<message>Car life work degree data.</message>\n</error_log>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (timestamp, level, message) 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:\ntimestamp = \"2026-01-22T04:03:04.968084\"\nlevel = \"ERROR\"\nmessage = \"Car life work degree data.\"\n",
"estimated_tokens": 165
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: ... | {
"format": "toml",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"prompt": "Create a TOML representation of lab result.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) 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:\nid = \"1ab423ce-853f-401e-b894-64de10fb74b0\"\ntest = \"you\"\nvalue = 46.705440705262\n",
"estimated_tokens": 152
} |
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"prompt": "Create a TOML representation of research paper.",
"output": "Approach:\n1. Define the schema: The research_paper should contain a dictionary with 6 root fields (paper_id, title, authors...) 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:\npaper_id = \"arXiv:2022.64333\"\ntitle = \"Business-focused fresh-thinking function\"\nabstract = \"Figure section so eat.\\nView many employee administration. End must order different. How speak study religious girl natural cost board.\"\nkeywords = [ \"whose\", \"pull\", \"per\", \"probably\", \"spring\",]\n[[authors]]\nname = \"Jeffrey Hughes\"\naffiliation = \"Davies-Wang\"\nemail = \"clarkjennifer@example.com\"\n\n[[authors]]\nname = \"Jimmy Sparks\"\naffiliation = \"Cole and Sons\"\nemail = \"caitlin45@example.org\"\n\n[[authors]]\nname = \"Amanda Baldwin\"\naffiliation = \"Fitzgerald Ltd\"\nemail = \"hmoore@example.net\"\n\n[publication]\nvenue = \"Science\"\nyear = 2024\ndoi = \"10.9540/MDWy\"\n",
"estimated_tokens": 298
} |
[
{
"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 error_log using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"prompt": "Output structured data for error_log using XML.",
"output": "Approach:\n1. Define the schema: The error_log should contain a dictionary with 5 root fields (timestamp, level, message...) 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<error_log>\n<timestamp>2026-01-22T04:03:07.315575</timestamp>\n<level>ERROR</level>\n<message>Anyone trip thus player thank will.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.315727</generated_at>\n<version>v4.0</version>\n<tags>lay</tags>\n<tags>moment</tags>\n<tags>paper</tags>\n<tags>charge</tags>\n<tags>so</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>william85</by>\n<timestamp>1974-04-08T19:46:38.582654</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>ogutierrez</by>\n<timestamp>1995-10-31T20:35:18.036308</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>david86</by>\n<timestamp>2010-06-08T05:13:57.827920</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 324
} |
[
{
"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",
"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>944afd9f-a035-46c9-9f03-7b6ea14c1588</rx>\n<drug>executive</drug>\n<dosage>10mg</dosage>\n</prescription>",
"estimated_tokens": 176
} |
[
{
"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 lab_result using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sc... | {
"format": "yaml",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"prompt": "Output structured data for lab_result using YAML.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) 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:\nid: 0d0bfcdd-43a6-4734-a3a3-2e84ac619a8e\ntest: health\nvalue: 22.736645656882736\n",
"estimated_tokens": 154
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Convert the following CSV to TOML:\ncompany,revenue,profit,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n... | {
"format": "toml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"prompt": "Convert the following CSV to TOML:\ncompany,revenue,profit,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n\"Collier, Davis and Foster\",916171,71292,2026-01-22T04:03:07.325400,v4.0,\"[\"\"than\"\", \"\"stand\"\", \"\"describe\"\", \"\"bill\"\", \"\"listen\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"robinsonsusan\"\", \"\"timestamp\"\": \"\"2018-12-19T11:56:49.503023\"\"}]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 5 root fields (company, revenue, profit...) 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:\ncompany = \"Collier, Davis and Foster\"\nrevenue = 916171\nprofit = 71292\n[[audit_log]]\naction = \"created\"\nby = \"robinsonsusan\"\ntimestamp = \"2018-12-19T11:56:49.503023\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.325400\"\nversion = \"v4.0\"\ntags = [ \"than\", \"stand\", \"describe\", \"bill\", \"listen\",]\n",
"estimated_tokens": 216
} |
[
{
"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 news_article using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "yaml",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"prompt": "Output structured data for news_article using YAML.",
"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: 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:\nheadline: Really style television analysis.\nbody: 'Pm reflect role build. Do ground participant film build data religious.\n\n Free station why and. Fill life threat lead assume serious assume. Remain return\n above visit.'\nauthor: Jose Garcia\n",
"estimated_tokens": 197
} |
[
{
"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 lab_result using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sc... | {
"format": "yaml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"prompt": "Output structured data for lab_result using YAML.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 5 root fields (id, test, value...) 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:\nid: 1edbab95-1c9e-468c-834b-f398ec8a08ac\ntest: resource\nvalue: 16.065436436624903\nmeta_info:\n generated_at: '2026-01-22T04:03:05.014341'\n version: v2.0\n tags:\n - author\n - top\n - reason\n - even\n - take\naudit_log:\n- action: created\n by: ijones\n timestamp: '1991-05-20T14:49:17.167016'\n- action: created\n by: angelwhite\n timestamp: '1998-01-17T13:19:47.558611'\n",
"estimated_tokens": 228
} |
[
{
"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 api_specification using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define th... | {
"format": "csv",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"prompt": "Output structured data for api_specification using CSV.",
"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: 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:\nendpoint,method,responses.200\r\n/api/v1/users,GET,OK\r\n",
"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": "Generate financial report data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schem... | {
"format": "json",
"complexity": "simple",
"schema": "financial_report",
"type": "generation",
"prompt": "Generate financial report data in JSON format.",
"output": "Approach:\n1. Define the schema: The financial_report should contain a dictionary with 3 root fields (company, revenue, profit) 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 \"company\": \"Miller, Strickland and Lee\",\n \"revenue\": 907554,\n \"profit\": 79706\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": "Transform this data from YAML to TOML:\nid: 59a2f510-a0d2-40d7-8ca2-04b10d909463\npatient: Anna Johnson\ndiagnosis: real\nnotes:... | {
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"prompt": "Transform this data from YAML to TOML:\nid: 59a2f510-a0d2-40d7-8ca2-04b10d909463\npatient: Anna Johnson\ndiagnosis: real\nnotes: 'Seven allow tree free. Stop instead however act single room.\n\n Night international item relationship successful. Those large above establish in\n describe.'\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 = \"59a2f510-a0d2-40d7-8ca2-04b10d909463\"\npatient = \"Anna Johnson\"\ndiagnosis = \"real\"\nnotes = \"Seven allow tree free. Stop instead however act single room.\\nNight international item relationship successful. Those large above establish in describe.\"\n",
"estimated_tokens": 204
} |
[
{
"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 lab_result using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schem... | {
"format": "csv",
"complexity": "simple",
"schema": "lab_result",
"type": "generation",
"prompt": "Output structured data for lab_result using CSV.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) and a nesting depth of 1.\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:\nid,test,value\r\n7716ced4-1e7f-4311-9bcb-41101453f974,painting,39.41475886335455\r\n",
"estimated_tokens": 158
} |
[
{
"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:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimi... | {
"format": "xml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"prompt": "Convert the following CSV to XML:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nEXP-764444,Analysis of land,0.8143,0.311,78,32,adam,0.001,2026-01-22T04:03:05.459141,v2.0,\"[\"\"pattern\"\", \"\"wide\"\", \"\"at\"\", \"\"step\"\", \"\"ahead\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"harrisjoseph\"\", \"\"timestamp\"\": \"\"1973-04-29T08:04:24.792312\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"uwalsh\"\", \"\"timestamp\"\": \"\"1978-03-29T09:36:00.148631\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"aramirez\"\", \"\"timestamp\"\": \"\"2024-06-26T06:47:17.411040\"\"}]\"\r\n",
"output": "Approach:\n1. Analyze the input CSV 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: 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<experiment_result>\n<experiment_id>EXP-764444</experiment_id>\n<title>Analysis of land</title>\n<metrics>\n<accuracy>0.8143</accuracy>\n<loss>0.311</loss>\n<epoch>78</epoch>\n</metrics>\n<config>\n<batch_size>32</batch_size>\n<optimizer>adam</optimizer>\n<lr>0.001</lr>\n</config>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.459141</generated_at>\n<version>v2.0</version>\n<tags>pattern</tags>\n<tags>wide</tags>\n<tags>at</tags>\n<tags>step</tags>\n<tags>ahead</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>harrisjoseph</by>\n<timestamp>1973-04-29T08:04:24.792312</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>uwalsh</by>\n<timestamp>1978-03-29T09:36:00.148631</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>aramirez</by>\n<timestamp>2024-06-26T06:47:17.411040</timestamp>\n</audit_log>\n</experiment_result>",
"estimated_tokens": 367
} |
[
{
"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 JSON to YAML:\n{\n \"course\": \"Polarized fresh-thinking framework\",\n \"weeks\": 11,\n \"credits\... | {
"format": "yaml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"prompt": "Transform this data from JSON to YAML:\n{\n \"course\": \"Polarized fresh-thinking framework\",\n \"weeks\": 11,\n \"credits\": 3,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.143414\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"job\",\n \"professional\",\n \"price\",\n \"once\",\n \"offer\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"tracey70\",\n \"timestamp\": \"2008-06-05T04:53:27.174089\"\n },\n {\n \"action\": \"created\",\n \"by\": \"jeffery54\",\n \"timestamp\": \"1984-12-14T02:13:43.404848\"\n },\n {\n \"action\": \"created\",\n \"by\": \"eross\",\n \"timestamp\": \"2014-01-16T14:33:28.535750\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (course, weeks, credits...) 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:\ncourse: Polarized fresh-thinking framework\nweeks: 11\ncredits: 3\nmeta_info:\n generated_at: '2026-01-22T04:03:05.143414'\n version: v2.0\n tags:\n - job\n - professional\n - price\n - once\n - offer\naudit_log:\n- action: created\n by: tracey70\n timestamp: '2008-06-05T04:53:27.174089'\n- action: created\n by: jeffery54\n timestamp: '1984-12-14T02:13:43.404848'\n- action: created\n by: eross\n timestamp: '2014-01-16T14:33:28.535750'\n",
"estimated_tokens": 252
} |
[
{
"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": "medium",
"schema": "prescription",
"type": "generation",
"prompt": "Output structured data for prescription using JSON.",
"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: 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\": \"1d4c1c1b-177b-489f-b58f-53f77587035d\",\n \"drug\": \"president\",\n \"dosage\": \"10mg\"\n}",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "csv",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"prompt": "Create a CSV representation of news article.",
"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: 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:\nheadline,body,author,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nDifference fear teach poor return account start.,\"Store hand next yes apply high president. Where produce draw cut way maintain.\nStandard son near. Expect cell into. Discover word try use increase.\",Lauren Bennett,2026-01-22T04:03:06.864511,v2.0,\"[\"\"she\"\", \"\"cup\"\", \"\"wife\"\", \"\"TV\"\", \"\"professional\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"kyoung\"\", \"\"timestamp\"\": \"\"1983-05-14T19:37:39.218645\"\"}]\"\r\n",
"estimated_tokens": 263
} |
[
{
"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": "complex",
"schema": "product_listing",
"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 5 root fields (product, price, stock...) 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:\nproduct = \"style\"\nprice = 54.2\nstock = 9\n[[audit_log]]\naction = \"created\"\nby = \"eforbes\"\ntimestamp = \"2003-05-05T01:51:54.050629\"\n\n[[audit_log]]\naction = \"created\"\nby = \"reginamurray\"\ntimestamp = \"2000-08-09T00:32:57.675589\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.393083\"\nversion = \"v5.0\"\ntags = [ \"season\", \"goal\", \"continue\", \"value\", \"other\",]\n",
"estimated_tokens": 225
} |
[
{
"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 YAML to XML:\nid: 3ab55f7b-ac16-4063-88be-8a7373e417d9\ntest: pick\nvalue: 51.26276332474761\n"
},
{
... | {
"format": "xml",
"complexity": "simple",
"schema": "lab_result",
"type": "conversion",
"prompt": "Convert the following YAML to XML:\nid: 3ab55f7b-ac16-4063-88be-8a7373e417d9\ntest: pick\nvalue: 51.26276332474761\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 3 root fields (id, test, value) 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<lab_result>\n<id>3ab55f7b-ac16-4063-88be-8a7373e417d9</id>\n<test>pick</test>\n<value>51.26276332474761</value>\n</lab_result>",
"estimated_tokens": 183
} |
[
{
"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 XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract>implement dynamic infrastr... | {
"format": "yaml",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"prompt": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract>implement dynamic infrastructures</contract>\n<parties>May-Brown</parties>\n<parties>Parks-Martinez</parties>\n<signed>False</signed>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.195191</generated_at>\n<version>v1.0</version>\n<tags>push</tags>\n<tags>owner</tags>\n<tags>next</tags>\n<tags>expert</tags>\n<tags>likely</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>sloanlouis</by>\n<timestamp>2009-02-16T18:44:04.763091</timestamp>\n</audit_log>\n</contract>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (contract, parties, signed...) 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:\ncontract: implement dynamic infrastructures\nparties:\n- May-Brown\n- Parks-Martinez\nsigned: false\nmeta_info:\n generated_at: '2026-01-22T04:03:07.195191'\n version: v1.0\n tags:\n - push\n - owner\n - next\n - expert\n - likely\naudit_log:\n- action: created\n by: sloanlouis\n timestamp: '2009-02-16T18:44:04.763091'\n",
"estimated_tokens": 223
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "yaml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"prompt": "Create a YAML 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: 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:\nendpoint: /api/v1/users\nmethod: GET\nresponses:\n '200': OK\nmeta_info:\n generated_at: '2026-01-22T04:03:06.629165'\n version: v2.0\n tags:\n - player\n - reveal\n - whether\n - new\n - race\naudit_log:\n- action: created\n by: nicole97\n timestamp: '2005-06-26T02:12:44.262468'\n- action: created\n by: sosadustin\n timestamp: '1986-07-31T10:37:07.098488'\n- action: created\n by: bradleygordon\n timestamp: '1999-06-04T06:35:40.934882'\n",
"estimated_tokens": 248
} |
[
{
"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:\nuser,post,likes\r\nrodriguezbreanna,Property wide whether color size arm. Development hug... | {
"format": "yaml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Transform this data from CSV to YAML:\nuser,post,likes\r\nrodriguezbreanna,Property wide whether color size arm. Development huge keep sometimes song side.,584\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (user, post, likes) 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: rodriguezbreanna\npost: Property wide whether color size arm. Development huge keep sometimes song side.\nlikes: 584\n",
"estimated_tokens": 172
} |
[
{
"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 transaction_record using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Defin... | {
"format": "json",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"prompt": "Output structured data for transaction_record using JSON.",
"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: 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 \"txn\": \"a7c2ec3a-958e-4d8a-a31a-0a31d026b509\",\n \"amount\": 212.62,\n \"status\": \"completed\"\n}",
"estimated_tokens": 161
} |
[
{
"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",
"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 = \"nicole97\"\ntimestamp = \"2005-06-26T02:12:44.262468\"\n\n[[audit_log]]\naction = \"created\"\nby = \"sosadustin\"\ntimestamp = \"1986-07-31T10:37:07.098488\"\n\n[[audit_log]]\naction = \"created\"\nby = \"bradleygordon\"\ntimestamp = \"1999-06-04T06:35:40.934882\"\n\n[responses]\n200 = \"OK\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.629165\"\nversion = \"v2.0\"\ntags = [ \"player\", \"reveal\", \"whether\", \"new\", \"race\",]\n",
"estimated_tokens": 256
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "csv",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"prompt": "Create a CSV representation of lab result.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) and a nesting depth of 1.\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:\nid,test,value\r\n30d5a0ab-5d9d-4f39-a83d-b88dd63aff62,if,39.84957755303192\r\n",
"estimated_tokens": 157
} |
[
{
"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 YAML to TOML:\nid: 5eda912e-90f6-4c61-a294-17b5db61fbee\ntest: direction\nvalue: 88.94549729365453\n"
... | {
"format": "toml",
"complexity": "medium",
"schema": "lab_result",
"type": "conversion",
"prompt": "Transform this data from YAML to TOML:\nid: 5eda912e-90f6-4c61-a294-17b5db61fbee\ntest: direction\nvalue: 88.94549729365453\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 3 root fields (id, test, value) 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 = \"5eda912e-90f6-4c61-a294-17b5db61fbee\"\ntest = \"direction\"\nvalue = 88.94549729365453\n",
"estimated_tokens": 161
} |
[
{
"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",
"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 = \"rodriguezjohnny\"\ntimestamp = \"1994-10-26T05:01:25.608282\"\n\n[[audit_log]]\naction = \"created\"\nby = \"victoriaadams\"\ntimestamp = \"1991-01-11T08:18:19.412188\"\n\n[[audit_log]]\naction = \"created\"\nby = \"daniel45\"\ntimestamp = \"1977-11-02T00:39:57.766938\"\n\n[responses]\n200 = \"OK\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.009064\"\nversion = \"v3.0\"\ntags = [ \"describe\", \"economic\", \"protect\", \"on\", \"through\",]\n",
"estimated_tokens": 259
} |
[
{
"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 XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course>Stand-alone optimi... | {
"format": "toml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"prompt": "Transform this data from XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course>Stand-alone optimizing moderator</course>\n<weeks>9</weeks>\n<credits>3</credits>\n</course_syllabus>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (course, weeks, credits) 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:\ncourse = \"Stand-alone optimizing moderator\"\nweeks = 9\ncredits = 3\n",
"estimated_tokens": 157
} |
[
{
"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 error_log using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"prompt": "Output structured data for error_log using TOML.",
"output": "Approach:\n1. Define the schema: The error_log should contain a dictionary with 3 root fields (timestamp, level, message) 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:\ntimestamp = \"2026-01-22T04:03:07.525501\"\nlevel = \"ERROR\"\nmessage = \"Return explain program try.\"\n",
"estimated_tokens": 158
} |
[
{
"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 XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Robert Lopez</... | {
"format": "toml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"prompt": "Transform this data from XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Robert Lopez</student>\n<score>6</score>\n<grade>B</grade>\n</student_assessment>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (student, score, grade) 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:\nstudent = \"Robert Lopez\"\nscore = 6\ngrade = \"B\"\n",
"estimated_tokens": 152
} |
[
{
"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 social_media_post using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define th... | {
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"prompt": "Output structured data for social_media_post using XML.",
"output": "Approach:\n1. Define the schema: The social_media_post should contain a dictionary with 3 root fields (user, post, likes) 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<social_media_post>\n<user>rodriguezbreanna</user>\n<post>Property wide whether color size arm. Development huge keep sometimes song side.</post>\n<likes>584</likes>\n</social_media_post>",
"estimated_tokens": 193
} |
[
{
"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 error_log using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "json",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"prompt": "Output structured data for error_log using JSON.",
"output": "Approach:\n1. Define the schema: The error_log should contain a dictionary with 3 root fields (timestamp, level, message) 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 \"timestamp\": \"2026-01-22T04:03:04.986223\",\n \"level\": \"ERROR\",\n \"message\": \"Section push resource city Republican society play.\"\n}",
"estimated_tokens": 170
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "yaml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"prompt": "Create a YAML representation of student assessment.",
"output": "Approach:\n1. Define the schema: The student_assessment should contain a dictionary with 3 root fields (student, score, grade) 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:\nstudent: Miranda Mcdaniel\nscore: 32\ngrade: C\n",
"estimated_tokens": 149
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate api specification data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"prompt": "Generate api specification data in JSON format.",
"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: 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}",
"estimated_tokens": 161
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate prescription data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "csv",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"prompt": "Generate prescription data in CSV format.",
"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: 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:\nrx,drug,dosage,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n1198f5d7-f258-4fd1-8771-647787dc3930,suddenly,10mg,2026-01-22T04:03:07.504169,v5.0,\"[\"\"produce\"\", \"\"sort\"\", \"\"himself\"\", \"\"with\"\", \"\"offer\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"hbrooks\"\", \"\"timestamp\"\": \"\"2021-11-02T15:23:12.349268\"\"}]\"\r\n",
"estimated_tokens": 221
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Down back poor number.</he... | {
"format": "csv",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"prompt": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Down back poor number.</headline>\n<body>Effect be sort interest civil move. Give sense decide fear.\nClose certainly beyond. Become political three official. Say more line close break image federal.</body>\n<author>Thomas Freeman</author>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.114403</generated_at>\n<version>v3.0</version>\n<tags>enough</tags>\n<tags>game</tags>\n<tags>that</tags>\n<tags>dinner</tags>\n<tags>east</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>amandajohnston</by>\n<timestamp>1975-04-06T18:52:31.060071</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>walshaaron</by>\n<timestamp>1976-12-15T21:48:33.039708</timestamp>\n</audit_log>\n</news_article>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (headline, body, author...) and a nesting depth of 3.\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:\nheadline,body,author,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nDown back poor number.,\"Effect be sort interest civil move. Give sense decide fear.\nClose certainly beyond. Become political three official. Say more line close break image federal.\",Thomas Freeman,2026-01-22T04:03:05.114403,v3.0,\"[\"\"enough\"\", \"\"game\"\", \"\"that\"\", \"\"dinner\"\", \"\"east\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"amandajohnston\"\", \"\"timestamp\"\": \"\"1975-04-06T18:52:31.060071\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"walshaaron\"\", \"\"timestamp\"\": \"\"1976-12-15T21:48:33.039708\"\"}]\"\r\n",
"estimated_tokens": 292
} |
[
{
"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:\nuser,post,likes\r\ncannonjennifer,Dark event poor effect including rise.,799\r\n"
},
{
... | {
"format": "json",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Convert the following CSV to JSON:\nuser,post,likes\r\ncannonjennifer,Dark event poor effect including rise.,799\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (user, post, likes) 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 \"user\": \"cannonjennifer\",\n \"post\": \"Dark event poor effect including rise.\",\n \"likes\": 799\n}",
"estimated_tokens": 166
} |
[
{
"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 TOML to JSON:\nrx = \"1e7156df-e8ee-4f29-8d6d-89eb18e67947\"\ndrug = \"side\"\ndosage = \"10mg\"\n[[audit_... | {
"format": "json",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"prompt": "Convert the following TOML to JSON:\nrx = \"1e7156df-e8ee-4f29-8d6d-89eb18e67947\"\ndrug = \"side\"\ndosage = \"10mg\"\n[[audit_log]]\naction = \"created\"\nby = \"awatts\"\ntimestamp = \"1982-02-18T13:51:21.020655\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.884826\"\nversion = \"v4.0\"\ntags = [ \"approach\", \"million\", \"long\", \"specific\", \"any\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (rx, drug, dosage...) 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 \"rx\": \"1e7156df-e8ee-4f29-8d6d-89eb18e67947\",\n \"drug\": \"side\",\n \"dosage\": \"10mg\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.884826\",\n \"version\": \"v4.0\",\n \"tags\": [\n \"approach\",\n \"million\",\n \"long\",\n \"specific\",\n \"any\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"awatts\",\n \"timestamp\": \"1982-02-18T13:51:21.020655\"\n }\n ]\n}",
"estimated_tokens": 246
} |
[
{
"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:\nuser: suzanne55\npost: Poor thus body himself very. Drug film another political school.\nli... | {
"format": "csv",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Transform this data from YAML to CSV:\nuser: suzanne55\npost: Poor thus body himself very. Drug film another political school.\nlikes: 795\nmeta_info:\n generated_at: '2026-01-22T04:03:07.677818'\n version: v2.0\n tags:\n - teach\n - change\n - particular\n - want\n - unit\naudit_log:\n- action: created\n by: nealchristy\n timestamp: '2017-09-07T19:26:46.742789'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (user, post, likes...) and a nesting depth of 3.\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:\nuser,post,likes,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nsuzanne55,Poor thus body himself very. Drug film another political school.,795,2026-01-22T04:03:07.677818,v2.0,\"[\"\"teach\"\", \"\"change\"\", \"\"particular\"\", \"\"want\"\", \"\"unit\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"nealchristy\"\", \"\"timestamp\"\": \"\"2017-09-07T19:26:46.742789\"\"}]\"\r\n",
"estimated_tokens": 236
} |
[
{
"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:\nstudent,score,grade\r\nBruce Lee,93,B\r\n"
},
{
"role": "assistant",
"content... | {
"format": "yaml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"prompt": "Transform this data from CSV to YAML:\nstudent,score,grade\r\nBruce Lee,93,B\r\n",
"output": "Approach:\n1. Analyze the input CSV 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: Bruce Lee\nscore: 93\ngrade: B\n",
"estimated_tokens": 152
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the YAML below into CSV:\nexperiment_id: EXP-804895\ntitle: Analysis of year\nmetrics:\n accuracy: 0.7691\n loss: 0.473... | {
"format": "csv",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"prompt": "Reformat the YAML below into CSV:\nexperiment_id: EXP-804895\ntitle: Analysis of year\nmetrics:\n accuracy: 0.7691\n loss: 0.473\n epoch: 50\nconfig:\n batch_size: 32\n optimizer: adam\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:06.038438'\n version: v4.0\n tags:\n - machine\n - employee\n - certainly\n - plan\n - official\naudit_log:\n- action: created\n by: jasonferguson\n timestamp: '1989-09-28T18:41:06.715987'\n- action: created\n by: georgekrista\n timestamp: '2012-10-29T22:34:19.270194'\n",
"output": "Approach:\n1. Analyze the input YAML 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: 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:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nEXP-804895,Analysis of year,0.7691,0.473,50,32,adam,0.001,2026-01-22T04:03:06.038438,v4.0,\"[\"\"machine\"\", \"\"employee\"\", \"\"certainly\"\", \"\"plan\"\", \"\"official\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jasonferguson\"\", \"\"timestamp\"\": \"\"1989-09-28T18:41:06.715987\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"georgekrista\"\", \"\"timestamp\"\": \"\"2012-10-29T22:34:19.270194\"\"}]\"\r\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": "Convert the following XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Me guy movie personal.... | {
"format": "toml",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"prompt": "Convert the following XML to TOML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Me guy movie personal.</headline>\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.</body>\n<author>John Gibson</author>\n</news_article>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (headline, body, author) 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:\nheadline = \"Me guy movie personal.\"\nbody = \"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.\"\nauthor = \"John Gibson\"\n",
"estimated_tokens": 205
} |
[
{
"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 lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: ... | {
"format": "json",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"prompt": "Create a JSON representation of lab result.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) 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 \"id\": \"4a13167f-d4f2-4211-b3b0-dd7bb0cacfe9\",\n \"test\": \"movement\",\n \"value\": 44.69633337985021\n}",
"estimated_tokens": 160
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate sales analytics data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "csv",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Generate sales analytics data in CSV format.",
"output": "Approach:\n1. Define the schema: The sales_analytics should contain a dictionary with 5 root fields (period, sales, region...) 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:\nperiod,sales,region,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nQ1,3206,South Matthewview,2026-01-22T04:03:06.074630,v3.0,\"[\"\"piece\"\", \"\"line\"\", \"\"be\"\", \"\"health\"\", \"\"street\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"william93\"\", \"\"timestamp\"\": \"\"2019-11-12T09:59:14.823296\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"michaelsmith\"\", \"\"timestamp\"\": \"\"1970-01-20T23:37:33.921965\"\"}]\"\r\n",
"estimated_tokens": 242
} |
[
{
"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 student_assessment using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "csv",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"prompt": "Output structured data for student_assessment using CSV.",
"output": "Approach:\n1. Define the schema: The student_assessment should contain a dictionary with 3 root fields (student, score, grade) and a nesting depth of 1.\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:\nstudent,score,grade\r\nAaron Nelson,39,B\r\n",
"estimated_tokens": 152
} |
[
{
"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:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\... | {
"format": "json",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"prompt": "Convert the following CSV to JSON:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r\narXiv:2022.12464,Organic hybrid time-frame,\"[{\"\"name\"\": \"\"Johnny Thomas\"\", \"\"affiliation\"\": \"\"Collins, Kim and Sexton\"\", \"\"email\"\": \"\"heather40@example.com\"\"}, {\"\"name\"\": \"\"Joseph Hansen\"\", \"\"affiliation\"\": \"\"Clements LLC\"\", \"\"email\"\": \"\"odeleon@example.com\"\"}, {\"\"name\"\": \"\"Parker Mullen\"\", \"\"affiliation\"\": \"\"Johnson-Watson\"\", \"\"email\"\": \"\"laurie68@example.org\"\"}, {\"\"name\"\": \"\"Patrick Gaines\"\", \"\"affiliation\"\": \"\"Scott, Parks and Torres\"\", \"\"email\"\": \"\"gmoreno@example.net\"\"}]\",\"Game bad inside young simple. Result more service. Learn fine fast establish from purpose.\nMoment total serious suggest always tax.\",\"[\"\"live\"\", \"\"sport\"\", \"\"prevent\"\", \"\"offer\"\"]\",ICLR,2021,10.8155/HVNG\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 6 root fields (paper_id, title, authors...) 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 \"paper_id\": \"arXiv:2022.12464\",\n \"title\": \"Organic hybrid time-frame\",\n \"authors\": [\n {\n \"name\": \"Johnny Thomas\",\n \"affiliation\": \"Collins, Kim and Sexton\",\n \"email\": \"heather40@example.com\"\n },\n {\n \"name\": \"Joseph Hansen\",\n \"affiliation\": \"Clements LLC\",\n \"email\": \"odeleon@example.com\"\n },\n {\n \"name\": \"Parker Mullen\",\n \"affiliation\": \"Johnson-Watson\",\n \"email\": \"laurie68@example.org\"\n },\n {\n \"name\": \"Patrick Gaines\",\n \"affiliation\": \"Scott, Parks and Torres\",\n \"email\": \"gmoreno@example.net\"\n }\n ],\n \"abstract\": \"Game bad inside young simple. Result more service. Learn fine fast establish from purpose.\\nMoment total serious suggest always tax.\",\n \"keywords\": [\n \"live\",\n \"sport\",\n \"prevent\",\n \"offer\"\n ],\n \"publication\": {\n \"venue\": \"ICLR\",\n \"year\": 2021,\n \"doi\": \"10.8155/HVNG\"\n }\n}",
"estimated_tokens": 371
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "csv",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"prompt": "Create a CSV 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: 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:\nendpoint,method,responses.200,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n/api/v1/users,GET,OK,2026-01-22T04:03:05.684994,v2.0,\"[\"\"behind\"\", \"\"down\"\", \"\"management\"\", \"\"conference\"\", \"\"one\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jimmypittman\"\", \"\"timestamp\"\": \"\"2001-05-25T00:14:30.193145\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"cowens\"\", \"\"timestamp\"\": \"\"1990-02-28T00:23:20.279383\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"smithjoshua\"\", \"\"timestamp\"\": \"\"2010-10-23T15:17:05.023169\"\"}]\"\r\n",
"estimated_tokens": 272
} |
[
{
"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<customer_review>\n<user>nichole49</user>\n<rati... | {
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"prompt": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>nichole49</user>\n<rating>3</rating>\n<comment>Phone phone series machine page race traditional.</comment>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.539337</generated_at>\n<version>v4.0</version>\n<tags>wait</tags>\n<tags>large</tags>\n<tags>business</tags>\n<tags>number</tags>\n<tags>young</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>jessica07</by>\n<timestamp>2017-07-05T03:45:59.622835</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>justinanderson</by>\n<timestamp>2011-07-01T21:39:10.009112</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>jessica79</by>\n<timestamp>1978-09-24T13:44:40.210898</timestamp>\n</audit_log>\n</customer_review>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (user, rating, comment...) 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 \"user\": \"nichole49\",\n \"rating\": 3,\n \"comment\": \"Phone phone series machine page race traditional.\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.539337\",\n \"version\": \"v4.0\",\n \"tags\": [\n \"wait\",\n \"large\",\n \"business\",\n \"number\",\n \"young\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"jessica07\",\n \"timestamp\": \"2017-07-05T03:45:59.622835\"\n },\n {\n \"action\": \"created\",\n \"by\": \"justinanderson\",\n \"timestamp\": \"2011-07-01T21:39:10.009112\"\n },\n {\n \"action\": \"created\",\n \"by\": \"jessica79\",\n \"timestamp\": \"1978-09-24T13:44:40.210898\"\n }\n ]\n}",
"estimated_tokens": 309
} |
[
{
"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 clinical_note using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the... | {
"format": "toml",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"prompt": "Output structured data for clinical_note using TOML.",
"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: 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:\nid = \"8e82e1dc-9c53-4d5a-9adf-9625870f9755\"\npatient = \"Lisa Williams\"\ndiagnosis = \"year\"\nnotes = \"Claim down still research attention rise language. Future rock company newspaper early character health. Campaign item brother cut several answer rate.\"\n[[audit_log]]\naction = \"created\"\nby = \"bthompson\"\ntimestamp = \"1997-10-21T14:42:41.378826\"\n\n[[audit_log]]\naction = \"created\"\nby = \"brooksphilip\"\ntimestamp = \"2019-04-07T12:02:39.475293\"\n\n[[audit_log]]\naction = \"created\"\nby = \"lsanders\"\ntimestamp = \"2016-06-10T07:35:22.439758\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.365431\"\nversion = \"v3.0\"\ntags = [ \"season\", \"mean\", \"heavy\", \"space\", \"receive\",]\n",
"estimated_tokens": 300
} |
[
{
"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 XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<financial_report>\n<company>Waller-Howell</comp... | {
"format": "yaml",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"prompt": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<financial_report>\n<company>Waller-Howell</company>\n<revenue>708536</revenue>\n<profit>31904</profit>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.439970</generated_at>\n<version>v4.0</version>\n<tags>view</tags>\n<tags>to</tags>\n<tags>medical</tags>\n<tags>agent</tags>\n<tags>behind</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>nrogers</by>\n<timestamp>1975-03-02T16:33:17.057565</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>mckenziekatherine</by>\n<timestamp>1973-12-04T00:25:30.953363</timestamp>\n</audit_log>\n</financial_report>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (company, revenue, profit...) 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:\ncompany: Waller-Howell\nrevenue: 708536\nprofit: 31904\nmeta_info:\n generated_at: '2026-01-22T04:03:07.439970'\n version: v4.0\n tags:\n - view\n - to\n - medical\n - agent\n - behind\naudit_log:\n- action: created\n by: nrogers\n timestamp: '1975-03-02T16:33:17.057565'\n- action: created\n by: mckenziekatherine\n timestamp: '1973-12-04T00:25:30.953363'\n",
"estimated_tokens": 232
} |
[
{
"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 error_log using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "json",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"prompt": "Output structured data for error_log using JSON.",
"output": "Approach:\n1. Define the schema: The error_log should contain a dictionary with 3 root fields (timestamp, level, message) 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 \"timestamp\": \"2026-01-22T04:03:05.824436\",\n \"level\": \"ERROR\",\n \"message\": \"Stock start business themselves whole meeting.\"\n}",
"estimated_tokens": 169
} |
[
{
"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 sales_analytics using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Output structured data for sales_analytics using XML.",
"output": "Approach:\n1. Define the schema: The sales_analytics should contain a dictionary with 5 root fields (period, sales, region...) 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<sales_analytics>\n<period>Q1</period>\n<sales>936</sales>\n<region>Hayeston</region>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.672988</generated_at>\n<version>v1.0</version>\n<tags>hope</tags>\n<tags>old</tags>\n<tags>executive</tags>\n<tags>maintain</tags>\n<tags>result</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>gonzaleznicole</by>\n<timestamp>1986-09-21T23:47:32.058050</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>kathycopeland</by>\n<timestamp>2004-06-24T13:32:22.284076</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>kolsen</by>\n<timestamp>2005-12-25T13:16:21.575744</timestamp>\n</audit_log>\n</sales_analytics>",
"estimated_tokens": 316
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this data from YAML to JSON:\nid: d07474d4-cfc4-405c-a3c2-b3a7a1931ac3\npatient: John Smith\ndiagnosis: pull\nnotes: P... | {
"format": "json",
"complexity": "complex",
"schema": "clinical_note",
"type": "conversion",
"prompt": "Transform this data from YAML to JSON:\nid: d07474d4-cfc4-405c-a3c2-b3a7a1931ac3\npatient: John Smith\ndiagnosis: pull\nnotes: Program education share friend kind agent late. Kitchen just upon call treat.\n Hit agreement happen world happen process.\nmeta_info:\n generated_at: '2026-01-22T04:03:07.162123'\n version: v1.0\n tags:\n - yard\n - per\n - while\n - apply\n - imagine\naudit_log:\n- action: created\n by: tanyafowler\n timestamp: '2025-12-13T15:32:12.283863'\n- action: created\n by: adrianwarren\n timestamp: '1995-07-01T02:47:10.686007'\n- action: created\n by: jasonyates\n timestamp: '1996-11-27T23:26:23.589631'\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: 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\": \"d07474d4-cfc4-405c-a3c2-b3a7a1931ac3\",\n \"patient\": \"John Smith\",\n \"diagnosis\": \"pull\",\n \"notes\": \"Program education share friend kind agent late. Kitchen just upon call treat. Hit agreement happen world happen process.\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:07.162123\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"yard\",\n \"per\",\n \"while\",\n \"apply\",\n \"imagine\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"tanyafowler\",\n \"timestamp\": \"2025-12-13T15:32:12.283863\"\n },\n {\n \"action\": \"created\",\n \"by\": \"adrianwarren\",\n \"timestamp\": \"1995-07-01T02:47:10.686007\"\n },\n {\n \"action\": \"created\",\n \"by\": \"jasonyates\",\n \"timestamp\": \"1996-11-27T23:26:23.589631\"\n }\n ]\n}",
"estimated_tokens": 341
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate clinical note data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "xml",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"prompt": "Generate clinical note data in XML format.",
"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: 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<clinical_note>\n<id>97990133-e976-41a2-ba52-cb26ffe01911</id>\n<patient>Craig Wolfe</patient>\n<diagnosis>leg</diagnosis>\n<notes>Position bring according article seat meet half. Time forget piece remember pull him.</notes>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.748879</generated_at>\n<version>v2.0</version>\n<tags>effort</tags>\n<tags>stage</tags>\n<tags>discuss</tags>\n<tags>develop</tags>\n<tags>analysis</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>vicki16</by>\n<timestamp>2012-08-28T15:41:07.241079</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>icarr</by>\n<timestamp>1977-04-26T02:49:35.739692</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>stacey86</by>\n<timestamp>1981-11-13T14:09:41.014136</timestamp>\n</audit_log>\n</clinical_note>",
"estimated_tokens": 347
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate api specification data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "yaml",
"complexity": "simple",
"schema": "api_specification",
"type": "generation",
"prompt": "Generate api specification data in YAML format.",
"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: 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:\nendpoint: /api/v1/users\nmethod: GET\nresponses:\n '200': OK\n",
"estimated_tokens": 154
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Convert the following JSON to CSV:\n{\n \"id\": \"63ad7c18-7dff-4568-a82d-c2fb3f013aac\",\n \"test\": \"before\",\n \"value\": ... | {
"format": "csv",
"complexity": "medium",
"schema": "lab_result",
"type": "conversion",
"prompt": "Convert the following JSON to CSV:\n{\n \"id\": \"63ad7c18-7dff-4568-a82d-c2fb3f013aac\",\n \"test\": \"before\",\n \"value\": 5.277298339631997\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: 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,test,value\r\n63ad7c18-7dff-4568-a82d-c2fb3f013aac,before,5.277298339631997\r\n",
"estimated_tokens": 165
} |
[
{
"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 XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>nduarte</user>\n<rating... | {
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"prompt": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>nduarte</user>\n<rating>3</rating>\n<comment>One able book state world political four risk.</comment>\n</customer_review>",
"output": "Approach:\n1. Analyze the input XML 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: nduarte\nrating: 3\ncomment: One able book state world political four risk.\n",
"estimated_tokens": 163
} |
[
{
"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:\npaper_id: arXiv:2023.17506\ntitle: User-friendly secondary paradigm\nauthors:\n- name: Susa... | {
"format": "csv",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"prompt": "Transform this data from YAML to CSV:\npaper_id: arXiv:2023.17506\ntitle: User-friendly secondary paradigm\nauthors:\n- name: Susan Myers\n affiliation: Carpenter-Hunt\n email: riddlemelissa@example.com\n- name: Zachary Davis\n affiliation: Kennedy, Walls and Heath\n email: lauren24@example.org\n- name: Earl Rogers\n affiliation: Carlson, Schmidt and Garcia\n email: saracook@example.org\nabstract: History sea worry pretty. President wide feeling serve run foreign. Health\n attorney military certain his. Support part together act radio.\nkeywords:\n- maintain\n- political\n- these\n- group\n- best\npublication:\n venue: NeurIPS\n year: 2021\n doi: 10.7725/uzzZ\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 6 root fields (paper_id, title, authors...) and a nesting depth of 3.\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:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r\narXiv:2023.17506,User-friendly secondary paradigm,\"[{\"\"name\"\": \"\"Susan Myers\"\", \"\"affiliation\"\": \"\"Carpenter-Hunt\"\", \"\"email\"\": \"\"riddlemelissa@example.com\"\"}, {\"\"name\"\": \"\"Zachary Davis\"\", \"\"affiliation\"\": \"\"Kennedy, Walls and Heath\"\", \"\"email\"\": \"\"lauren24@example.org\"\"}, {\"\"name\"\": \"\"Earl Rogers\"\", \"\"affiliation\"\": \"\"Carlson, Schmidt and Garcia\"\", \"\"email\"\": \"\"saracook@example.org\"\"}]\",History sea worry pretty. President wide feeling serve run foreign. Health attorney military certain his. Support part together act radio.,\"[\"\"maintain\"\", \"\"political\"\", \"\"these\"\", \"\"group\"\", \"\"best\"\"]\",NeurIPS,2021,10.7725/uzzZ\r\n",
"estimated_tokens": 327
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the CSV below into TOML:\ncourse,weeks,credits\r\nImplemented cohesive orchestration,12,3\r\n"
},
{
"role": "as... | {
"format": "toml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"prompt": "Reformat the CSV below into TOML:\ncourse,weeks,credits\r\nImplemented cohesive orchestration,12,3\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (course, weeks, credits) 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:\ncourse = \"Implemented cohesive orchestration\"\nweeks = 12\ncredits = 3\n",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the TOML below into CSV:\ncontract = \"enable dynamic metrics\"\nparties = [ \"Peck PLC\", \"Hebert Ltd\",]\nsigned = tru... | {
"format": "csv",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"prompt": "Reformat the TOML below into CSV:\ncontract = \"enable dynamic metrics\"\nparties = [ \"Peck PLC\", \"Hebert Ltd\",]\nsigned = true\n[[audit_log]]\naction = \"created\"\nby = \"dianahernandez\"\ntimestamp = \"1978-01-22T22:30:29.872276\"\n\n[[audit_log]]\naction = \"created\"\nby = \"rodriguezmichael\"\ntimestamp = \"2022-02-15T22:38:00.640042\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.928942\"\nversion = \"v3.0\"\ntags = [ \"life\", \"religious\", \"choose\", \"throughout\", \"continue\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (contract, parties, signed...) and a nesting depth of 3.\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:\ncontract,parties,signed,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nenable dynamic metrics,\"[\"\"Peck PLC\"\", \"\"Hebert Ltd\"\"]\",True,2026-01-22T04:03:05.928942,v3.0,\"[\"\"life\"\", \"\"religious\"\", \"\"choose\"\", \"\"throughout\"\", \"\"continue\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"dianahernandez\"\", \"\"timestamp\"\": \"\"1978-01-22T22:30:29.872276\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"rodriguezmichael\"\", \"\"timestamp\"\": \"\"2022-02-15T22:38:00.640042\"\"}]\"\r\n",
"estimated_tokens": 265
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract>grow real-time e-markets</cont... | {
"format": "csv",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"prompt": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract>grow real-time e-markets</contract>\n<parties>Romero-Hoover</parties>\n<parties>Nolan, Harper and Lewis</parties>\n<signed>False</signed>\n</contract>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\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:\ncontract,parties,signed\r\ngrow real-time e-markets,\"[\"\"Romero-Hoover\"\", \"\"Nolan, Harper and Lewis\"\"]\",False\r\n",
"estimated_tokens": 175
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate api specification data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "csv",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"prompt": "Generate api specification data in CSV 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: 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:\nendpoint,method,responses.200,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\n/api/v1/users,GET,OK,2026-01-22T04:03:06.089918,v2.0,\"[\"\"leader\"\", \"\"decide\"\", \"\"floor\"\", \"\"line\"\", \"\"turn\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jamie17\"\", \"\"timestamp\"\": \"\"2019-09-20T22:46:19.493464\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"yhubbard\"\", \"\"timestamp\"\": \"\"1991-06-08T07:56:10.014566\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"jessicajones\"\", \"\"timestamp\"\": \"\"1988-12-17T17:54:12.937796\"\"}]\"\r\n",
"estimated_tokens": 269
} |
[
{
"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": "medium",
"schema": "api_specification",
"type": "generation",
"prompt": "Create a JSON representation of api specification.",
"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: 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}",
"estimated_tokens": 161
} |
[
{
"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 TOML to CSV:\nproduct = \"part\"\nprice = 81.35\nstock = 42\n"
},
{
"role": "assistant",
"con... | {
"format": "csv",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"prompt": "Transform this data from TOML to CSV:\nproduct = \"part\"\nprice = 81.35\nstock = 42\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (product, price, stock) 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:\nproduct,price,stock\r\npart,81.35,42\r\n",
"estimated_tokens": 156
} |
[
{
"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 course_syllabus using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "csv",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"prompt": "Output structured data for course_syllabus using CSV.",
"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: 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:\ncourse,weeks,credits\r\nFace-to-face directional info-mediaries,9,3\r\n",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate experiment result data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"prompt": "Generate experiment result data in YAML format.",
"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-611510\ntitle: Analysis of side\nmetrics:\n accuracy: 0.7285\n loss: 0.478\n epoch: 56\nconfig:\n batch_size: 32\n optimizer: adam\n lr: 0.001\nmeta_info:\n generated_at: '2026-01-22T04:03:07.512068'\n version: v1.0\n tags:\n - candidate\n - his\n - represent\n - Democrat\n - nor\naudit_log:\n- action: created\n by: sarah01\n timestamp: '2016-09-16T00:41:23.531490'\n- action: created\n by: dtorres\n timestamp: '2022-06-20T09:35:37.910739'\n- action: created\n by: tranhunter\n timestamp: '1980-02-19T10:39:08.302765'\n",
"estimated_tokens": 273
} |
[
{
"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 lab_result using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schem... | {
"format": "xml",
"complexity": "simple",
"schema": "lab_result",
"type": "generation",
"prompt": "Output structured data for lab_result using XML.",
"output": "Approach:\n1. Define the schema: The lab_result should contain a dictionary with 3 root fields (id, test, value) 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<lab_result>\n<id>7301a4df-9a3e-4620-b997-fd62584c98fb</id>\n<test>hold</test>\n<value>45.46268797137946</value>\n</lab_result>",
"estimated_tokens": 176
} |
Subsets and Splits
Format and Complexity Counts
Groups training examples by their format and complexity metadata to reveal patterns in dataset structure and potentially identify undersampled combinations that could inform data balancing strategies.