messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"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 sales_analytics using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Output structured data for sales_analytics using JSON.",
"output": "Approach:\n1. Define the schema: The sales_analytics should contain a dictionary with 3 root fields (period, sales, region) and a nesting depth of 1.\n2. Select the format: 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 \"period\": \"Q1\",\n \"sales\": 2234,\n \"region\": \"North Mitchell\"\n}",
"estimated_tokens": 154
} |
[
{
"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": "simple",
"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 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Select the format: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"experiment_id\": \"EXP-802887\",\n \"title\": \"Analysis of especially\",\n \"metrics\": {\n \"accuracy\": 0.7219,\n \"loss\": 0.4423,\n \"epoch\": 59\n },\n \"config\": {\n \"batch_size\": 64,\n \"optimizer\": \"adam\",\n \"lr\": 0.001\n }\n}",
"estimated_tokens": 199
} |
[
{
"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": "medium",
"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 3 root fields (headline, body, author) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Republican respond individual town east.</headline>\n<body>Appear religious Republican member from store. Store note benefit spring ask key energy. House identify back.\nMy seek suggest care movement anyone. Difference control perform good.</body>\n<author>Tommy Porter</author>\n</news_article>",
"estimated_tokens": 226
} |
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "json",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"prompt": "Create a JSON representation of social media post.",
"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: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"user\": \"robin72\",\n \"post\": \"Ball moment really less. Walk want laugh management produce lose. Themselves shake measure create last focus.\",\n \"likes\": 239,\n \"meta_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\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"sean67\",\n \"timestamp\": \"2009-04-02T11:37:07.729349\"\n },\n {\n \"action\": \"created\",\n \"by\": \"pearsonsarah\",\n \"timestamp\": \"1995-08-13T15:47:45.614852\"\n }\n ]\n}",
"estimated_tokens": 286
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate contract data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The c... | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"prompt": "Generate contract data in TOML format.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: 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:\ncontract = \"synthesize world-class info-mediaries\"\nparties = [ \"Greene, Hayes and Jones\", \"Henson Group\",]\nsigned = true\n",
"estimated_tokens": 164
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate contract data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The c... | {
"format": "json",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"prompt": "Generate contract data in JSON format.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 5 root fields (contract, parties, signed...) 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 \"contract\": \"engineer robust portals\",\n \"parties\": [\n \"Boyle Ltd\",\n \"Bauer, Knight and Hendricks\"\n ],\n \"signed\": true,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:06.355425\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"local\",\n \"image\",\n \"catch\",\n \"shoulder\",\n \"cup\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"nbennett\",\n \"timestamp\": \"1975-12-20T12:18:09.387573\"\n },\n {\n \"action\": \"created\",\n \"by\": \"batesmichelle\",\n \"timestamp\": \"1972-03-01T04:11:41.463965\"\n }\n ]\n}",
"estimated_tokens": 280
} |
[
{
"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 XML to CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>patrickvilla</user>\n<rati... | {
"format": "csv",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"prompt": "Convert the following XML to CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>patrickvilla</user>\n<rating>1</rating>\n<comment>Determine case career white use institution.</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: 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,rating,comment\r\npatrickvilla,1,Determine case career white use institution.\r\n",
"estimated_tokens": 167
} |
[
{
"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 prescription using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"prompt": "Output structured data for prescription using XML.",
"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>0a25dfe7-54d1-4268-8410-2cf64bf21278</rx>\n<drug>machine</drug>\n<dosage>10mg</dosage>\n</prescription>",
"estimated_tokens": 175
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate lab result data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "json",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"prompt": "Generate lab result data in JSON 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: 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\": \"c0aaf1fd-c7eb-4b3d-a193-a7e3710ea7e4\",\n \"test\": \"arrive\",\n \"value\": 51.98103152763387,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.581261\",\n \"version\": \"v5.0\",\n \"tags\": [\n \"fear\",\n \"sure\",\n \"others\",\n \"true\",\n \"live\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"michaeldillon\",\n \"timestamp\": \"1995-02-24T14:57:02.180456\"\n },\n {\n \"action\": \"created\",\n \"by\": \"amyjones\",\n \"timestamp\": \"2005-10-07T17:03:45.026273\"\n },\n {\n \"action\": \"created\",\n \"by\": \"brentmoore\",\n \"timestamp\": \"2005-12-08T21:09:37.589715\"\n }\n ]\n}",
"estimated_tokens": 297
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the JSON below into TOML:\n{\n \"id\": \"5eda912e-90f6-4c61-a294-17b5db61fbee\",\n \"test\": \"direction\",\n \"valu... | {
"format": "toml",
"complexity": "medium",
"schema": "lab_result",
"type": "conversion",
"prompt": "Reformat the JSON below into TOML:\n{\n \"id\": \"5eda912e-90f6-4c61-a294-17b5db61fbee\",\n \"test\": \"direction\",\n \"value\": 88.94549729365453\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: 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 XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following CSV to XML:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r\n... | {
"format": "xml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"prompt": "Convert the following CSV to XML:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r\narXiv:2021.34450,Fully-configurable actuating groupware,\"[{\"\"name\"\": \"\"Donna Frank\"\", \"\"affiliation\"\": \"\"Rojas, Williams and Richardson\"\", \"\"email\"\": \"\"[email protected]\"\"}, {\"\"name\"\": \"\"Brittney Morgan\"\", \"\"affiliation\"\": \"\"Jimenez, Nguyen and Alexander\"\", \"\"email\"\": \"\"[email protected]\"\"}, {\"\"name\"\": \"\"Daniel Wallace\"\", \"\"affiliation\"\": \"\"Kemp Inc\"\", \"\"email\"\": \"\"[email protected]\"\"}, {\"\"name\"\": \"\"Anna Brown\"\", \"\"affiliation\"\": \"\"Willis-Nelson\"\", \"\"email\"\": \"\"[email protected]\"\"}]\",Cup response major green western phone these despite. Suddenly doctor process area general. Under news bed direction deal evening. Administration cut worry range create.,\"[\"\"realize\"\", \"\"each\"\", \"\"carry\"\", \"\"before\"\"]\",ICLR,2021,10.6815/ONgL\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: 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<research_paper>\n<paper_id>arXiv:2021.34450</paper_id>\n<title>Fully-configurable actuating groupware</title>\n<authors>\n<name>Donna Frank</name>\n<affiliation>Rojas, Williams and Richardson</affiliation>\n<email>[email protected]</email>\n</authors>\n<authors>\n<name>Brittney Morgan</name>\n<affiliation>Jimenez, Nguyen and Alexander</affiliation>\n<email>[email protected]</email>\n</authors>\n<authors>\n<name>Daniel Wallace</name>\n<affiliation>Kemp Inc</affiliation>\n<email>[email protected]</email>\n</authors>\n<authors>\n<name>Anna Brown</name>\n<affiliation>Willis-Nelson</affiliation>\n<email>[email protected]</email>\n</authors>\n<abstract>Cup response major green western phone these despite. Suddenly doctor process area general. Under news bed direction deal evening. Administration cut worry range create.</abstract>\n<keywords>realize</keywords>\n<keywords>each</keywords>\n<keywords>carry</keywords>\n<keywords>before</keywords>\n<publication>\n<venue>ICLR</venue>\n<year>2021</year>\n<doi>10.6815/ONgL</doi>\n</publication>\n</research_paper>",
"estimated_tokens": 418
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate customer review data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "csv",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Generate customer review data in CSV 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: 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:\nuser,rating,comment\r\nmontespriscilla,2,Without use audience go one.\r\n",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course>Grass-roots dynamic pr... | {
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"prompt": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course>Grass-roots dynamic project</course>\n<weeks>11</weeks>\n<credits>3</credits>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.915610</generated_at>\n<version>v2.0</version>\n<tags>man</tags>\n<tags>poor</tags>\n<tags>wrong</tags>\n<tags>morning</tags>\n<tags>teach</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>uperry</by>\n<timestamp>1993-09-14T14:23:30.232959</timestamp>\n</audit_log>\n</course_syllabus>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (course, weeks, credits...) and a nesting depth of 3.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"course\": \"Grass-roots dynamic project\",\n \"weeks\": 11,\n \"credits\": 3,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:06.915610\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"man\",\n \"poor\",\n \"wrong\",\n \"morning\",\n \"teach\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"uperry\",\n \"timestamp\": \"1993-09-14T14:23:30.232959\"\n }\n ]\n}",
"estimated_tokens": 242
} |
[
{
"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:06.341804</timestamp>\n<level>ERROR</level>\n<message>Quality edge sister increase candidate push.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.341947</generated_at>\n<version>v1.0</version>\n<tags>citizen</tags>\n<tags>certainly</tags>\n<tags>interest</tags>\n<tags>might</tags>\n<tags>race</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>robertbishop</by>\n<timestamp>2025-07-08T16:57:17.127346</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>oramos</by>\n<timestamp>1992-01-05T20:33:34.910222</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>amy06</by>\n<timestamp>1971-06-03T06:00:16.965589</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 328
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate experiment result data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "csv",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"prompt": "Generate experiment result data in CSV 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: 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\r\nEXP-871872,Analysis of list,0.8202,0.2852,77,64,sgd,0.001\r\n",
"estimated_tokens": 186
} |
[
{
"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 product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "toml",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"prompt": "Create a TOML 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: 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 = \"natural\"\nprice = 17.08\nstock = 24\n[[audit_log]]\naction = \"created\"\nby = \"dpalmer\"\ntimestamp = \"1999-08-30T22:23:01.982747\"\n\n[[audit_log]]\naction = \"created\"\nby = \"darlenemorris\"\ntimestamp = \"2022-01-22T04:18:21.865191\"\n\n[[audit_log]]\naction = \"created\"\nby = \"kenneth21\"\ntimestamp = \"1981-11-26T16:34:59.117882\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.521445\"\nversion = \"v4.0\"\ntags = [ \"sense\", \"effect\", \"stock\", \"suggest\", \"order\",]\n",
"estimated_tokens": 249
} |
[
{
"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:\ncontract: integrate ubiquitous solutions\nparties:\n- Taylor LLC\n- Martinez, Perez and Flores\... | {
"format": "csv",
"complexity": "complex",
"schema": "contract",
"type": "conversion",
"prompt": "Reformat the YAML below into CSV:\ncontract: integrate ubiquitous solutions\nparties:\n- Taylor LLC\n- Martinez, Perez and Flores\nsigned: true\nmeta_info:\n generated_at: '2026-01-22T04:03:05.090235'\n version: v1.0\n tags:\n - war\n - strong\n - major\n - five\n - red\naudit_log:\n- action: created\n by: johnsonsharon\n timestamp: '1994-05-08T11:39:13.740004'\n- action: created\n by: craigcruz\n timestamp: '1994-03-12T14:03:40.493862'\n- action: created\n by: gerald72\n timestamp: '1978-07-01T03:17:30.156308'\n",
"output": "Approach:\n1. Analyze the input YAML 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\nintegrate ubiquitous solutions,\"[\"\"Taylor LLC\"\", \"\"Martinez, Perez and Flores\"\"]\",True,2026-01-22T04:03:05.090235,v1.0,\"[\"\"war\"\", \"\"strong\"\", \"\"major\"\", \"\"five\"\", \"\"red\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"johnsonsharon\"\", \"\"timestamp\"\": \"\"1994-05-08T11:39:13.740004\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"craigcruz\"\", \"\"timestamp\"\": \"\"1994-03-12T14:03:40.493862\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"gerald72\"\", \"\"timestamp\"\": \"\"1978-07-01T03:17:30.156308\"\"}]\"\r\n",
"estimated_tokens": 289
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the CSV below into YAML:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r... | {
"format": "yaml",
"complexity": "simple",
"schema": "research_paper",
"type": "conversion",
"prompt": "Reformat the CSV below into YAML:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi\r\narXiv:2021.89200,Proactive cohesive budgetary management,\"[{\"\"name\"\": \"\"Kathy Rodriguez\"\", \"\"affiliation\"\": \"\"Romero, Franco and Taylor\"\", \"\"email\"\": \"\"[email protected]\"\"}, {\"\"name\"\": \"\"Mr. John Herman\"\", \"\"affiliation\"\": \"\"Shannon, Peterson and Torres\"\", \"\"email\"\": \"\"[email protected]\"\"}]\",\"Another her find system executive arm often century. Bill thought mouth water church.\nPattern three section exactly. Teach type water could. Develop similar machine wonder agency wonder.\",\"[\"\"support\"\", \"\"pattern\"\", \"\"room\"\", \"\"inside\"\", \"\"conference\"\", \"\"be\"\"]\",Science,2021,10.5194/Nznc\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: 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:\npaper_id: arXiv:2021.89200\ntitle: Proactive cohesive budgetary management\nauthors:\n- name: Kathy Rodriguez\n affiliation: Romero, Franco and Taylor\n email: [email protected]\n- name: Mr. John Herman\n affiliation: Shannon, Peterson and Torres\n email: [email protected]\nabstract: 'Another her find system executive arm often century. Bill thought mouth\n water church.\n\n Pattern three section exactly. Teach type water could. Develop similar machine wonder\n agency wonder.'\nkeywords:\n- support\n- pattern\n- room\n- inside\n- conference\n- be\npublication:\n venue: Science\n year: 2021\n doi: 10.5194/Nznc\n",
"estimated_tokens": 296
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate prescription data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"prompt": "Generate prescription data in TOML 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: 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 = \"cc11ba92-4294-42c2-b903-2a38469292dd\"\ndrug = \"television\"\ndosage = \"10mg\"\n[[audit_log]]\naction = \"created\"\nby = \"lgoodwin\"\ntimestamp = \"1991-08-02T21:25:59.699347\"\n\n[[audit_log]]\naction = \"created\"\nby = \"hubermarcia\"\ntimestamp = \"1984-09-29T03:50:56.757272\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.734304\"\nversion = \"v1.0\"\ntags = [ \"lead\", \"factor\", \"quickly\", \"task\", \"piece\",]\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": "Create a JSON representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sc... | {
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"prompt": "Create a JSON representation of financial report.",
"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\": \"Chapman Ltd\",\n \"revenue\": 198278,\n \"profit\": 55646\n}",
"estimated_tokens": 155
} |
[
{
"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 sales_analytics using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Output structured data for sales_analytics using JSON.",
"output": "Approach:\n1. Define the schema: The sales_analytics should contain a dictionary with 3 root fields (period, sales, region) and a nesting depth of 1.\n2. Select the format: 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 \"period\": \"Q1\",\n \"sales\": 2733,\n \"region\": \"Port Donald\"\n}",
"estimated_tokens": 153
} |
[
{
"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": "complex",
"schema": "prescription",
"type": "generation",
"prompt": "Generate prescription data in XML 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: 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>d544240b-ba58-4b05-b5df-21e945b08f3f</rx>\n<drug>pick</drug>\n<dosage>10mg</dosage>\n<meta_info>\n<generated_at>2026-01-22T04:03:04.972428</generated_at>\n<version>v2.0</version>\n<tags>ok</tags>\n<tags>military</tags>\n<tags>analysis</tags>\n<tags>including</tags>\n<tags>race</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>samuelbarker</by>\n<timestamp>1995-11-08T06:54:44.784320</timestamp>\n</audit_log>\n</prescription>",
"estimated_tokens": 257
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the XML below into YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<social_media_post>\n<user>erika28</user>\n<post>... | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Reformat the XML below into YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<social_media_post>\n<user>erika28</user>\n<post>Her bag compare training rock. Report gun expert sell sense family join.</post>\n<likes>630</likes>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.738412</generated_at>\n<version>v3.0</version>\n<tags>stay</tags>\n<tags>care</tags>\n<tags>reality</tags>\n<tags>finally</tags>\n<tags>machine</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>othompson</by>\n<timestamp>1989-04-02T23:26:21.127447</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>richardsloan</by>\n<timestamp>2001-04-14T09:51:05.899817</timestamp>\n</audit_log>\n</social_media_post>",
"output": "Approach:\n1. Analyze the input XML structure: It represents a dictionary with 5 root fields (user, post, likes...) 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:\nuser: erika28\npost: Her bag compare training rock. Report gun expert sell sense family join.\nlikes: 630\nmeta_info:\n generated_at: '2026-01-22T04:03:05.738412'\n version: v3.0\n tags:\n - stay\n - care\n - reality\n - finally\n - machine\naudit_log:\n- action: created\n by: othompson\n timestamp: '1989-04-02T23:26:21.127447'\n- action: created\n by: richardsloan\n timestamp: '2001-04-14T09:51:05.899817'\n",
"estimated_tokens": 244
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate lab result data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "json",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"prompt": "Generate lab result data in JSON format.",
"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\": \"9fa69ad5-b955-4818-8a6b-336559f91558\",\n \"test\": \"hotel\",\n \"value\": 26.851058350115487\n}",
"estimated_tokens": 159
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: Th... | {
"format": "toml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"prompt": "Create a TOML representation of contract.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 5 root fields (contract, parties, signed...) 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:\ncontract = \"extend extensible niches\"\nparties = [ \"Perez, Martinez and Brown\", \"Thompson, Robbins and Moore\",]\nsigned = true\n[[audit_log]]\naction = \"created\"\nby = \"jonathanclark\"\ntimestamp = \"1991-05-02T11:27:45.070964\"\n\n[[audit_log]]\naction = \"created\"\nby = \"brittneylyons\"\ntimestamp = \"1995-03-20T08:52:20.538798\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.106846\"\nversion = \"v3.0\"\ntags = [ \"something\", \"minute\", \"choose\", \"affect\", \"film\",]\n",
"estimated_tokens": 247
} |
[
{
"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": "medium",
"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-100053</experiment_id>\n<title>Analysis of hour</title>\n<metrics>\n<accuracy>0.791</accuracy>\n<loss>0.43</loss>\n<epoch>30</epoch>\n</metrics>\n<config>\n<batch_size>32</batch_size>\n<optimizer>sgd</optimizer>\n<lr>0.001</lr>\n</config>\n</experiment_result>",
"estimated_tokens": 223
} |
[
{
"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": "simple",
"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 3 root fields (txn, amount, status) 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:\ntxn,amount,status\r\n8e22c006-968b-41bd-9166-be6cef1785f6,361.88,completed\r\n",
"estimated_tokens": 160
} |
[
{
"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\": \"1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1\",\n \"drug\": \"me\",\n \"dosage\": \"10... | {
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"prompt": "Reformat the JSON below into XML:\n{\n \"rx\": \"1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1\",\n \"drug\": \"me\",\n \"dosage\": \"10mg\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.190126\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"suddenly\",\n \"those\",\n \"experience\",\n \"each\",\n \"seem\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"lewisapril\",\n \"timestamp\": \"1990-03-27T18:23:16.981344\"\n },\n {\n \"action\": \"created\",\n \"by\": \"hjohnson\",\n \"timestamp\": \"1990-08-17T03:08:04.190155\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (rx, drug, dosage...) 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<prescription>\n<rx>1a8dfd53-621a-4d2c-9f33-ca7ee32f26e1</rx>\n<drug>me</drug>\n<dosage>10mg</dosage>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.190126</generated_at>\n<version>v1.0</version>\n<tags>suddenly</tags>\n<tags>those</tags>\n<tags>experience</tags>\n<tags>each</tags>\n<tags>seem</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>lewisapril</by>\n<timestamp>1990-03-27T18:23:16.981344</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>hjohnson</by>\n<timestamp>1990-08-17T03:08:04.190155</timestamp>\n</audit_log>\n</prescription>",
"estimated_tokens": 293
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate course syllabus data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "csv",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"prompt": "Generate course syllabus data in CSV format.",
"output": "Approach:\n1. Define the schema: The course_syllabus should contain a dictionary with 3 root fields (course, weeks, credits) and a nesting depth of 1.\n2. Select the format: 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\nStand-alone optimizing moderator,9,3\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": "Generate customer review data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "csv",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Generate customer review data in CSV 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: 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:\nuser,rating,comment\r\nsmithchristopher,4,Candidate her glass poor tonight.\r\n",
"estimated_tokens": 160
} |
[
{
"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 \"id\": \"e9fac959-4109-44a1-9d15-24c94330f744\",\n \"patient\": \"Troy Swanson\",\n ... | {
"format": "yaml",
"complexity": "complex",
"schema": "clinical_note",
"type": "conversion",
"prompt": "Convert the following JSON to YAML:\n{\n \"id\": \"e9fac959-4109-44a1-9d15-24c94330f744\",\n \"patient\": \"Troy Swanson\",\n \"diagnosis\": \"before\",\n \"notes\": \"Wind research me detail. Subject adult law organization. Really never the early and life.\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.848657\",\n \"version\": \"v3.0\",\n \"tags\": [\n \"create\",\n \"friend\",\n \"today\",\n \"soldier\",\n \"exist\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"dmills\",\n \"timestamp\": \"2002-12-23T09:28:34.591544\"\n },\n {\n \"action\": \"created\",\n \"by\": \"jmcpherson\",\n \"timestamp\": \"1989-07-19T11:54:33.383757\"\n },\n {\n \"action\": \"created\",\n \"by\": \"jgray\",\n \"timestamp\": \"2016-07-02T17:32:40.677221\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 6 root fields (id, patient, diagnosis...) 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:\nid: e9fac959-4109-44a1-9d15-24c94330f744\npatient: Troy Swanson\ndiagnosis: before\nnotes: Wind research me detail. Subject adult law organization. Really never the early\n and life.\nmeta_info:\n generated_at: '2026-01-22T04:03:05.848657'\n version: v3.0\n tags:\n - create\n - friend\n - today\n - soldier\n - exist\naudit_log:\n- action: created\n by: dmills\n timestamp: '2002-12-23T09:28:34.591544'\n- action: created\n by: jmcpherson\n timestamp: '1989-07-19T11:54:33.383757'\n- action: created\n by: jgray\n timestamp: '2016-07-02T17:32:40.677221'\n",
"estimated_tokens": 281
} |
[
{
"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:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.opti... | {
"format": "toml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"prompt": "Reformat the CSV below into TOML:\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",
"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: TOML requires strict syntax. Define hierarchy using dot-notation or [section] headers.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\nexperiment_id = \"EXP-750115\"\ntitle = \"Analysis of art\"\n[[audit_log]]\naction = \"created\"\nby = \"chadfowler\"\ntimestamp = \"2001-12-16T07:09:33.116073\"\n\n[[audit_log]]\naction = \"created\"\nby = \"amandaprice\"\ntimestamp = \"2025-03-14T03:49:51.874209\"\n\n[[audit_log]]\naction = \"created\"\nby = \"susanmeyers\"\ntimestamp = \"1973-07-26T23:46:43.783834\"\n\n[metrics]\naccuracy = 0.8804\nloss = 0.4258\nepoch = 67\n\n[config]\nbatch_size = 64\noptimizer = \"adam\"\nlr = 0.001\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.457781\"\nversion = \"v2.0\"\ntags = [ \"agree\", \"small\", \"tax\", \"participant\", \"lose\",]\n",
"estimated_tokens": 287
} |
[
{
"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 JSON to TOML:\n{\n \"user\": \"robin72\",\n \"post\": \"Ball moment really less. Walk want laugh managem... | {
"format": "toml",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Convert the following JSON to TOML:\n{\n \"user\": \"robin72\",\n \"post\": \"Ball moment really less. Walk want laugh management produce lose. Themselves shake measure create last focus.\",\n \"likes\": 239,\n \"meta_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\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"sean67\",\n \"timestamp\": \"2009-04-02T11:37:07.729349\"\n },\n {\n \"action\": \"created\",\n \"by\": \"pearsonsarah\",\n \"timestamp\": \"1995-08-13T15:47:45.614852\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (user, post, likes...) 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:\nuser = \"robin72\"\npost = \"Ball moment really less. Walk want laugh management produce lose. Themselves shake measure create last focus.\"\nlikes = 239\n[[audit_log]]\naction = \"created\"\nby = \"sean67\"\ntimestamp = \"2009-04-02T11:37:07.729349\"\n\n[[audit_log]]\naction = \"created\"\nby = \"pearsonsarah\"\ntimestamp = \"1995-08-13T15:47:45.614852\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:05.086673\"\nversion = \"v5.0\"\ntags = [ \"couple\", \"film\", \"gun\", \"build\", \"pull\",]\n",
"estimated_tokens": 255
} |
[
{
"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 JSON to TOML:\n{\n \"txn\": \"fba32437-3ed4-4acf-bcd8-2a975d997700\",\n \"amount\": 248.65,\n \"status\... | {
"format": "toml",
"complexity": "simple",
"schema": "transaction_record",
"type": "conversion",
"prompt": "Convert the following JSON to TOML:\n{\n \"txn\": \"fba32437-3ed4-4acf-bcd8-2a975d997700\",\n \"amount\": 248.65,\n \"status\": \"completed\"\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (txn, amount, status) 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:\ntxn = \"fba32437-3ed4-4acf-bcd8-2a975d997700\"\namount = 248.65\nstatus = \"completed\"\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 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\nefa82ca6-ea4c-417c-80e7-b01530ea0616,172.91,completed,2026-01-22T04:03:07.744438,v2.0,\"[\"\"help\"\", \"\"forward\"\", \"\"activity\"\", \"\"operation\"\", \"\"item\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"zimmermanolivia\"\", \"\"timestamp\"\": \"\"1994-05-29T03:41:21.085532\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"katherineanderson\"\", \"\"timestamp\"\": \"\"2001-07-12T21:54:43.553344\"\"}]\"\r\n",
"estimated_tokens": 254
} |
[
{
"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": "simple",
"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 3 root fields (period, sales, region) 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:\nperiod,sales,region\r\nQ1,3171,Markmouth\r\n",
"estimated_tokens": 151
} |
[
{
"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:\ntimestamp = \"2026-01-22T04:03:05.395954\"\nlevel = \"ERROR\"\nmessage = \"For next arrive.... | {
"format": "csv",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"prompt": "Transform this data from TOML to CSV:\ntimestamp = \"2026-01-22T04:03:05.395954\"\nlevel = \"ERROR\"\nmessage = \"For next arrive.\"\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (timestamp, level, message) 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:\ntimestamp,level,message\r\n2026-01-22T04:03:05.395954,ERROR,For next arrive.\r\n",
"estimated_tokens": 167
} |
[
{
"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": "medium",
"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 4 root fields (id, patient, diagnosis...) 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<clinical_note>\n<id>709596e8-9c88-4c54-99d6-361f90141992</id>\n<patient>Kristi Smith</patient>\n<diagnosis>pressure</diagnosis>\n<notes>Media situation stay team professional sea. According new seat produce table. Mind north give enjoy law. Field rich people prepare.</notes>\n</clinical_note>",
"estimated_tokens": 220
} |
[
{
"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 news_article using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "xml",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"prompt": "Output structured data for news_article using XML.",
"output": "Approach:\n1. Define the schema: The news_article should contain a dictionary with 3 root fields (headline, body, author) and a nesting depth of 1.\n2. Select the format: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<headline>Long perform yet suddenly fly sport.</headline>\n<body>Child tend draw make possible. Where visit whole financial carry. Task particularly give let.\nInterview story power price low. Determine character third speak.</body>\n<author>Dr. Martha Ferguson DDS</author>\n</news_article>",
"estimated_tokens": 223
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Transform this data from JSON to TOML:\n{\n \"rx\": \"757226a4-a9e3-4b60-9f5d-2af01f823f75\",\n \"drug\": \"various\",\n \"do... | {
"format": "toml",
"complexity": "simple",
"schema": "prescription",
"type": "conversion",
"prompt": "Transform this data from JSON to TOML:\n{\n \"rx\": \"757226a4-a9e3-4b60-9f5d-2af01f823f75\",\n \"drug\": \"various\",\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: 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 = \"757226a4-a9e3-4b60-9f5d-2af01f823f75\"\ndrug = \"various\"\ndosage = \"10mg\"\n",
"estimated_tokens": 159
} |
[
{
"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 customer_review using JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "json",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Output structured data for customer_review using JSON.",
"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: JSON is chosen. Ensure all keys are quoted and nested structures use curly braces.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n{\n \"user\": \"brittany57\",\n \"rating\": 3,\n \"comment\": \"Last sport begin east environment heavy common.\"\n}",
"estimated_tokens": 163
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product>take</product>\n<pric... | {
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"prompt": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product>take</product>\n<price>21.21</price>\n<stock>9</stock>\n</product_listing>",
"output": "Approach:\n1. Analyze the input XML 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\": \"take\",\n \"price\": 21.21,\n \"stock\": 9\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": "Generate research paper data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: Th... | {
"format": "csv",
"complexity": "complex",
"schema": "research_paper",
"type": "generation",
"prompt": "Generate research paper data in CSV format.",
"output": "Approach:\n1. Define the schema: The research_paper should contain a dictionary with 8 root fields (paper_id, title, authors...) 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:\npaper_id,title,authors,abstract,keywords,publication.venue,publication.year,publication.doi,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\narXiv:2023.34237,Synergistic eco-centric extranet,\"[{\"\"name\"\": \"\"Robert Ross\"\", \"\"affiliation\"\": \"\"Hill, Warner and Williams\"\", \"\"email\"\": \"\"[email protected]\"\"}, {\"\"name\"\": \"\"Jeffrey Marshall\"\", \"\"affiliation\"\": \"\"Molina-Castro\"\", \"\"email\"\": \"\"[email protected]\"\"}]\",Single section many question. From method thing yet forget of through. Book firm today yet. Guy draw tell marriage where none body.,\"[\"\"total\"\", \"\"hour\"\", \"\"doctor\"\"]\",NeurIPS,2020,10.2147/hysY,2026-01-22T04:03:06.537801,v3.0,\"[\"\"himself\"\", \"\"rate\"\", \"\"owner\"\", \"\"board\"\", \"\"prove\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"williamortiz\"\", \"\"timestamp\"\": \"\"1991-11-23T14:56:12.593186\"\"}]\"\r\n",
"estimated_tokens": 348
} |
[
{
"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 TOML to CSV:\nperiod = \"Q1\"\nsales = 3439\nregion = \"Mendozaton\"\n[[audit_log]]\naction = \"created\"\nb... | {
"format": "csv",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"prompt": "Convert the following TOML to CSV:\nperiod = \"Q1\"\nsales = 3439\nregion = \"Mendozaton\"\n[[audit_log]]\naction = \"created\"\nby = \"harrisonmichele\"\ntimestamp = \"1985-06-17T07:04:09.996283\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.135459\"\nversion = \"v2.0\"\ntags = [ \"training\", \"agree\", \"hard\", \"sound\", \"discover\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (period, sales, region...) 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:\nperiod,sales,region,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nQ1,3439,Mendozaton,2026-01-22T04:03:06.135459,v2.0,\"[\"\"training\"\", \"\"agree\"\", \"\"hard\"\", \"\"sound\"\", \"\"discover\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"harrisonmichele\"\", \"\"timestamp\"\": \"\"1985-06-17T07:04:09.996283\"\"}]\"\r\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": "Create a XML representation of error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"prompt": "Create a XML representation of error log.",
"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:06.699723</timestamp>\n<level>ERROR</level>\n<message>Research recently college street imagine memory discuss.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.699816</generated_at>\n<version>v2.0</version>\n<tags>push</tags>\n<tags>cultural</tags>\n<tags>establish</tags>\n<tags>pull</tags>\n<tags>hit</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>cody95</by>\n<timestamp>2015-02-04T15:33:29.237874</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 270
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate sales analytics data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: T... | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Generate sales analytics data in XML 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: 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>1293</sales>\n<region>East Luke</region>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.493282</generated_at>\n<version>v3.0</version>\n<tags>always</tags>\n<tags>someone</tags>\n<tags>guy</tags>\n<tags>financial</tags>\n<tags>thought</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>warrenlauren</by>\n<timestamp>1982-02-19T17:59:18.620684</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>robertblackburn</by>\n<timestamp>1976-03-29T15:21:16.808589</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>csuarez</by>\n<timestamp>2013-08-27T14:23:21.257692</timestamp>\n</audit_log>\n</sales_analytics>",
"estimated_tokens": 317
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the s... | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"prompt": "Create a TOML 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: 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 = \"samuel28\"\ntimestamp = \"1995-07-12T23:55:29.516704\"\n\n[[audit_log]]\naction = \"created\"\nby = \"cclark\"\ntimestamp = \"2014-06-22T01:59:11.617325\"\n\n[[audit_log]]\naction = \"created\"\nby = \"christopherdelgado\"\ntimestamp = \"2005-07-17T08:58:55.611609\"\n\n[responses]\n200 = \"OK\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.641166\"\nversion = \"v4.0\"\ntags = [ \"outside\", \"foot\", \"peace\", \"yeah\", \"future\",]\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": "Generate social media post data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "csv",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"prompt": "Generate social media post data in CSV format.",
"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: 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:\nuser,post,likes\r\nkpowers,Article stage how final development receive front. Perhaps forward scientist need. Agree such civil loss agent those child very.,909\r\n",
"estimated_tokens": 180
} |
[
{
"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 JSON to CSV:\n{\n \"company\": \"Flores Inc\",\n \"revenue\": 134921,\n \"profit\": 4518,\n \"meta_in... | {
"format": "csv",
"complexity": "complex",
"schema": "financial_report",
"type": "conversion",
"prompt": "Transform this data from JSON to CSV:\n{\n \"company\": \"Flores Inc\",\n \"revenue\": 134921,\n \"profit\": 4518,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:07.002947\",\n \"version\": \"v4.0\",\n \"tags\": [\n \"expect\",\n \"best\",\n \"rate\",\n \"institution\",\n \"soldier\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"gallen\",\n \"timestamp\": \"1976-04-21T12:32:05.995925\"\n },\n {\n \"action\": \"created\",\n \"by\": \"spencerichard\",\n \"timestamp\": \"2007-09-26T16:41:58.460941\"\n },\n {\n \"action\": \"created\",\n \"by\": \"wilsonmark\",\n \"timestamp\": \"2006-09-17T11:02:41.887642\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (company, revenue, profit...) 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:\ncompany,revenue,profit,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nFlores Inc,134921,4518,2026-01-22T04:03:07.002947,v4.0,\"[\"\"expect\"\", \"\"best\"\", \"\"rate\"\", \"\"institution\"\", \"\"soldier\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"gallen\"\", \"\"timestamp\"\": \"\"1976-04-21T12:32:05.995925\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"spencerichard\"\", \"\"timestamp\"\": \"\"2007-09-26T16:41:58.460941\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"wilsonmark\"\", \"\"timestamp\"\": \"\"2006-09-17T11:02:41.887642\"\"}]\"\r\n",
"estimated_tokens": 275
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the CSV below into JSON:\ncontract,parties,signed\r\nmorph compelling vortals,\"[\"\"Ray, Gallegos and Morse\"\", \"\"G... | {
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"prompt": "Reformat the CSV below into JSON:\ncontract,parties,signed\r\nmorph compelling vortals,\"[\"\"Ray, Gallegos and Morse\"\", \"\"Graham-Flores\"\"]\",False\r\n",
"output": "Approach:\n1. Analyze the input CSV structure: It represents a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Identify the target format requirements: JSON requires strict syntax. Ensure all keys are quoted and nested structures use curly braces.\n3. Map the fields: The root keys will map directly, while nested objects need careful formatting.\n4. Handle data types: Ensure strings, numbers, and booleans are formatted correctly for the target.\n5. Construct the output: serialized the data strictly following the target schema.\n\nOutput:\n{\n \"contract\": \"morph compelling vortals\",\n \"parties\": [\n \"Ray, Gallegos and Morse\",\n \"Graham-Flores\"\n ],\n \"signed\": false\n}",
"estimated_tokens": 177
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate contract data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The c... | {
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"prompt": "Generate contract data in YAML format.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: YAML is chosen. Use indentation to represent nesting. lists are denoted by hyphens.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\ncontract: target e-business mindshare\nparties:\n- Cox PLC\n- Nichols PLC\nsigned: true\n",
"estimated_tokens": 157
} |
[
{
"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 customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "xml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Create a XML representation of customer review.",
"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: 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<customer_review>\n<user>smithchristopher</user>\n<rating>4</rating>\n<comment>Candidate her glass poor tonight.</comment>\n</customer_review>",
"estimated_tokens": 182
} |
[
{
"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 research_paper using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define th... | {
"format": "yaml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"prompt": "Output structured data for research_paper using YAML.",
"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: 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:\npaper_id: arXiv:2021.34450\ntitle: Fully-configurable actuating groupware\nauthors:\n- name: Donna Frank\n affiliation: Rojas, Williams and Richardson\n email: [email protected]\n- name: Brittney Morgan\n affiliation: Jimenez, Nguyen and Alexander\n email: [email protected]\n- name: Daniel Wallace\n affiliation: Kemp Inc\n email: [email protected]\n- name: Anna Brown\n affiliation: Willis-Nelson\n email: [email protected]\nabstract: Cup response major green western phone these despite. Suddenly doctor process\n area general. Under news bed direction deal evening. Administration cut worry range\n create.\nkeywords:\n- realize\n- each\n- carry\n- before\npublication:\n venue: ICLR\n year: 2021\n doi: 10.6815/ONgL\n",
"estimated_tokens": 320
} |
[
{
"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 contract using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sche... | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"prompt": "Output structured data for contract using TOML.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\n2. Select the format: 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:\ncontract = \"implement dynamic experiences\"\nparties = [ \"Lynn-Ponce\", \"Moore Group\",]\nsigned = true\n",
"estimated_tokens": 159
} |
[
{
"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 \"experiment_id\": \"EXP-134623\",\n \"title\": \"Analysis of local\",\n \"metrics\": {\... | {
"format": "xml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"prompt": "Reformat the JSON below into XML:\n{\n \"experiment_id\": \"EXP-134623\",\n \"title\": \"Analysis of local\",\n \"metrics\": {\n \"accuracy\": 0.8729,\n \"loss\": 0.3973,\n \"epoch\": 86\n },\n \"config\": {\n \"batch_size\": 32,\n \"optimizer\": \"adam\",\n \"lr\": 0.001\n },\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:06.992992\",\n \"version\": \"v1.0\",\n \"tags\": [\n \"record\",\n \"read\",\n \"fire\",\n \"collection\",\n \"discuss\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"hsmith\",\n \"timestamp\": \"1998-04-26T19:18:39.970484\"\n },\n {\n \"action\": \"created\",\n \"by\": \"dhorn\",\n \"timestamp\": \"1975-12-12T14:34:20.683729\"\n },\n {\n \"action\": \"created\",\n \"by\": \"qruiz\",\n \"timestamp\": \"2015-08-13T14:59:05.917332\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 6 root fields (experiment_id, title, metrics...) and a nesting depth of 3.\n2. Identify the target format requirements: 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-134623</experiment_id>\n<title>Analysis of local</title>\n<metrics>\n<accuracy>0.8729</accuracy>\n<loss>0.3973</loss>\n<epoch>86</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:06.992992</generated_at>\n<version>v1.0</version>\n<tags>record</tags>\n<tags>read</tags>\n<tags>fire</tags>\n<tags>collection</tags>\n<tags>discuss</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>hsmith</by>\n<timestamp>1998-04-26T19:18:39.970484</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>dhorn</by>\n<timestamp>1975-12-12T14:34:20.683729</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>qruiz</by>\n<timestamp>2015-08-13T14:59:05.917332</timestamp>\n</audit_log>\n</experiment_result>",
"estimated_tokens": 367
} |
[
{
"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 prescription using XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"prompt": "Output structured data for prescription using XML.",
"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: 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>1e7156df-e8ee-4f29-8d6d-89eb18e67947</rx>\n<drug>side</drug>\n<dosage>10mg</dosage>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.884826</generated_at>\n<version>v4.0</version>\n<tags>approach</tags>\n<tags>million</tags>\n<tags>long</tags>\n<tags>specific</tags>\n<tags>any</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>awatts</by>\n<timestamp>1982-02-18T13:51:21.020655</timestamp>\n</audit_log>\n</prescription>",
"estimated_tokens": 256
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Transform this data from JSON to TOML:\n{\n \"contract\": \"target e-business mindshare\",\n \"parties\": [\n \"Cox PLC\",\... | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"prompt": "Transform this data from JSON to TOML:\n{\n \"contract\": \"target e-business mindshare\",\n \"parties\": [\n \"Cox PLC\",\n \"Nichols PLC\"\n ],\n \"signed\": true\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (contract, parties, signed) and a nesting depth of 2.\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:\ncontract = \"target e-business mindshare\"\nparties = [ \"Cox PLC\", \"Nichols PLC\",]\nsigned = true\n",
"estimated_tokens": 165
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Analyze the data structure and generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>dmendez</user>\n<rating>... | {
"format": "json",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"prompt": "Reformat the XML below into JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<user>dmendez</user>\n<rating>2</rating>\n<comment>Up show best country trade.</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: 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\": \"dmendez\",\n \"rating\": 2,\n \"comment\": \"Up show best country trade.\"\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": "Output structured data for product_listing using CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "csv",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"prompt": "Output structured data for product_listing using CSV.",
"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: 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\r\nfund,77.36,37\r\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": "Create a XML representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"prompt": "Create a XML representation of product listing.",
"output": "Approach:\n1. Define the schema: The product_listing should contain a dictionary with 3 root fields (product, price, stock) and a nesting depth of 1.\n2. Select the format: 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<product_listing>\n<product>take</product>\n<price>21.21</price>\n<stock>9</stock>\n</product_listing>",
"estimated_tokens": 172
} |
[
{
"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 news_article using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "toml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"prompt": "Output structured data for news_article using TOML.",
"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: 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:\nheadline = \"Billion language industry read already.\"\nbody = \"Boy in knowledge expert laugh task develop image. Too fill rich dark process keep. Receive cover common military.\"\nauthor = \"James Greer\"\n[[audit_log]]\naction = \"created\"\nby = \"singhjennifer\"\ntimestamp = \"2007-05-28T08:14:54.033351\"\n\n[[audit_log]]\naction = \"created\"\nby = \"alexkirk\"\ntimestamp = \"1979-05-04T19:28:18.100842\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.589378\"\nversion = \"v2.0\"\ntags = [ \"nation\", \"figure\", \"partner\", \"character\", \"road\",]\n",
"estimated_tokens": 265
} |
[
{
"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: 2b568954-97d6-4dd1-ba22-750995ffec2e\npatient: Kenneth Clark\ndiagnosis: market\nnot... | {
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"type": "conversion",
"prompt": "Transform this data from YAML to TOML:\nid: 2b568954-97d6-4dd1-ba22-750995ffec2e\npatient: Kenneth Clark\ndiagnosis: market\nnotes: 'Camera third local conference seat series generation. Base skin play write\n husband democratic. Force friend consider difference.\n\n Actually deal worry.'\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 = \"2b568954-97d6-4dd1-ba22-750995ffec2e\"\npatient = \"Kenneth Clark\"\ndiagnosis = \"market\"\nnotes = \"Camera third local conference seat series generation. Base skin play write husband democratic. Force friend consider difference.\\nActually deal worry.\"\n",
"estimated_tokens": 205
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the TOML below into XML:\nexperiment_id = \"EXP-548343\"\ntitle = \"Analysis of special\"\n\n[metrics]\naccuracy = 0.9516... | {
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"type": "conversion",
"prompt": "Reformat the TOML below into XML:\nexperiment_id = \"EXP-548343\"\ntitle = \"Analysis of special\"\n\n[metrics]\naccuracy = 0.9516\nloss = 0.2734\nepoch = 49\n\n[config]\nbatch_size = 64\noptimizer = \"sgd\"\nlr = 0.001\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 4 root fields (experiment_id, title, metrics...) and a nesting depth of 2.\n2. Identify the target format requirements: 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-548343</experiment_id>\n<title>Analysis of special</title>\n<metrics>\n<accuracy>0.9516</accuracy>\n<loss>0.2734</loss>\n<epoch>49</epoch>\n</metrics>\n<config>\n<batch_size>64</batch_size>\n<optimizer>sgd</optimizer>\n<lr>0.001</lr>\n</config>\n</experiment_result>",
"estimated_tokens": 230
} |
[
{
"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 = \"a8e177de-cc08-42c2-b674-4f4eeb95e280\"\ndrug = \"we\"\ndosage = \"10mg\"\n",
"estimated_tokens": 151
} |
[
{
"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": "simple",
"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: a7ba27d4-6ddf-46a0-a86e-027c70722f7c\ntest: beautiful\nvalue: 90.65628902840275\n",
"estimated_tokens": 155
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the TOML below into XML:\ntimestamp = \"2026-01-22T04:03:07.445501\"\nlevel = \"ERROR\"\nmessage = \"Imagine old son week... | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"prompt": "Reformat the TOML below into XML:\ntimestamp = \"2026-01-22T04:03:07.445501\"\nlevel = \"ERROR\"\nmessage = \"Imagine old son week meeting enough some.\"\n[[audit_log]]\naction = \"created\"\nby = \"beth21\"\ntimestamp = \"1970-02-23T07:26:30.736477\"\n\n[[audit_log]]\naction = \"created\"\nby = \"alexander79\"\ntimestamp = \"1977-07-25T17:38:54.720502\"\n\n[[audit_log]]\naction = \"created\"\nby = \"karen19\"\ntimestamp = \"1973-08-08T14:49:26.934075\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.445650\"\nversion = \"v4.0\"\ntags = [ \"give\", \"a\", \"same\", \"speech\", \"treat\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (timestamp, level, message...) and a nesting depth of 3.\n2. Identify the target format requirements: 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<error_log>\n<timestamp>2026-01-22T04:03:07.445501</timestamp>\n<level>ERROR</level>\n<message>Imagine old son week meeting enough some.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:07.445650</generated_at>\n<version>v4.0</version>\n<tags>give</tags>\n<tags>a</tags>\n<tags>same</tags>\n<tags>speech</tags>\n<tags>treat</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>beth21</by>\n<timestamp>1970-02-23T07:26:30.736477</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>alexander79</by>\n<timestamp>1977-07-25T17:38:54.720502</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>karen19</by>\n<timestamp>1973-08-08T14:49:26.934075</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 332
} |
[
{
"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\": \"49703d47-cb81-4af5-a7f9-0094479b8ca2\",\n \"drug\": \"traditional\",\n \"dosage\": \"10mg\"\n}",
"estimated_tokens": 159
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate clinical note data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: ... | {
"format": "yaml",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"prompt": "Generate clinical note data in YAML format.",
"output": "Approach:\n1. Define the schema: The clinical_note should contain a dictionary with 4 root fields (id, patient, diagnosis...) 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: 1d9061f2-fb53-4be8-acad-6da5016ea71d\npatient: Jon Hawkins\ndiagnosis: fear\nnotes: 'Once sell station between office wall popular. When there shoulder.\n\n Live these personal activity. Road teach concern. Song theory story total note suddenly\n already international.'\n",
"estimated_tokens": 205
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output structured data for sales_analytics using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "yaml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Output structured data for sales_analytics using YAML.",
"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: 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:\nperiod: Q1\nsales: 3561\nregion: Port Stephenland\nmeta_info:\n generated_at: '2026-01-22T04:03:07.170825'\n version: v3.0\n tags:\n - image\n - member\n - hand\n - white\n - budget\naudit_log:\n- action: created\n by: timothy58\n timestamp: '2005-05-27T00:40:00.129404'\n- action: created\n by: ogreen\n timestamp: '2011-08-12T13:28:23.354063'\n- action: created\n by: dorseywesley\n timestamp: '1986-09-06T23:45:06.025388'\n",
"estimated_tokens": 242
} |
[
{
"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 contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: Th... | {
"format": "toml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"prompt": "Create a TOML representation of contract.",
"output": "Approach:\n1. Define the schema: The contract should contain a dictionary with 5 root fields (contract, parties, signed...) 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:\ncontract = \"implement dynamic infrastructures\"\nparties = [ \"May-Brown\", \"Parks-Martinez\",]\nsigned = false\n[[audit_log]]\naction = \"created\"\nby = \"sloanlouis\"\ntimestamp = \"2009-02-16T18:44:04.763091\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.195191\"\nversion = \"v1.0\"\ntags = [ \"push\", \"owner\", \"next\", \"expert\", \"likely\",]\n",
"estimated_tokens": 216
} |
[
{
"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": "complex",
"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 5 root fields (user, post, likes...) 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<social_media_post>\n<user>erika28</user>\n<post>Her bag compare training rock. Report gun expert sell sense family join.</post>\n<likes>630</likes>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.738412</generated_at>\n<version>v3.0</version>\n<tags>stay</tags>\n<tags>care</tags>\n<tags>reality</tags>\n<tags>finally</tags>\n<tags>machine</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>othompson</by>\n<timestamp>1989-04-02T23:26:21.127447</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>richardsloan</by>\n<timestamp>2001-04-14T09:51:05.899817</timestamp>\n</audit_log>\n</social_media_post>",
"estimated_tokens": 301
} |
[
{
"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 \"user\": \"villanuevamichael\",\n \"post\": \"Development popular town left whole new... | {
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Reformat the JSON below into YAML:\n{\n \"user\": \"villanuevamichael\",\n \"post\": \"Development popular town left whole news fight. Baby it I into both. Choice town whether that top sport son.\",\n \"likes\": 804,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:06.892984\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"same\",\n \"rise\",\n \"center\",\n \"simple\",\n \"attorney\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"thompsonmaurice\",\n \"timestamp\": \"2010-01-05T05:40:06.951333\"\n },\n {\n \"action\": \"created\",\n \"by\": \"reginamiles\",\n \"timestamp\": \"1995-08-21T13:36:49.268333\"\n },\n {\n \"action\": \"created\",\n \"by\": \"trevorthompson\",\n \"timestamp\": \"2023-06-08T15:07:48.194939\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (user, post, likes...) 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:\nuser: villanuevamichael\npost: Development popular town left whole news fight. Baby it I into both. Choice\n town whether that top sport son.\nlikes: 804\nmeta_info:\n generated_at: '2026-01-22T04:03:06.892984'\n version: v2.0\n tags:\n - same\n - rise\n - center\n - simple\n - attorney\naudit_log:\n- action: created\n by: thompsonmaurice\n timestamp: '2010-01-05T05:40:06.951333'\n- action: created\n by: reginamiles\n timestamp: '1995-08-21T13:36:49.268333'\n- action: created\n by: trevorthompson\n timestamp: '2023-06-08T15:07:48.194939'\n",
"estimated_tokens": 277
} |
[
{
"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": "medium",
"schema": "prescription",
"type": "generation",
"prompt": "Generate prescription data in CSV 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: 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\r\n76ed4160-aee0-4fa9-be06-d25ed12fd4da,foot,10mg\r\n",
"estimated_tokens": 155
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this data from JSON to XML:\n{\n \"rx\": \"65b40a28-dd76-4b2c-9db4-5f1edb82705f\",\n \"drug\": \"sell\",\n \"dosage\"... | {
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"prompt": "Transform this data from JSON to XML:\n{\n \"rx\": \"65b40a28-dd76-4b2c-9db4-5f1edb82705f\",\n \"drug\": \"sell\",\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>65b40a28-dd76-4b2c-9db4-5f1edb82705f</rx>\n<drug>sell</drug>\n<dosage>10mg</dosage>\n</prescription>",
"estimated_tokens": 181
} |
[
{
"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 \"txn\": \"d648f31b-e4e9-4678-872b-5f6416b767ae\",\n \"amount\": 136.38,\n \"status\": \... | {
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "conversion",
"prompt": "Reformat the JSON below into XML:\n{\n \"txn\": \"d648f31b-e4e9-4678-872b-5f6416b767ae\",\n \"amount\": 136.38,\n \"status\": \"completed\"\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 3 root fields (txn, amount, status) 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<transaction_record>\n<txn>d648f31b-e4e9-4678-872b-5f6416b767ae</txn>\n<amount>136.38</amount>\n<status>completed</status>\n</transaction_record>",
"estimated_tokens": 188
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate clinical note data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The... | {
"format": "csv",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"prompt": "Generate clinical note data in CSV format.",
"output": "Approach:\n1. Define the schema: The clinical_note should contain a dictionary with 4 root fields (id, patient, diagnosis...) 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,patient,diagnosis,notes\r\n1c1d2b21-40c0-4182-8aa0-b31a184ec31b,Justin Reyes,take,\"Party card fall smile. Area person shake money outside statement.\nItem account democratic do project. More lay customer tend. Size thousand carry hard conference court.\"\r\n",
"estimated_tokens": 205
} |
[
{
"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 JSON to XML:\n{\n \"endpoint\": \"/api/v1/users\",\n \"method\": \"GET\",\n \"responses\": {\n \"200\"... | {
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"prompt": "Convert the following JSON to XML:\n{\n \"endpoint\": \"/api/v1/users\",\n \"method\": \"GET\",\n \"responses\": {\n \"200\": \"OK\"\n },\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.057559\",\n \"version\": \"v3.0\",\n \"tags\": [\n \"respond\",\n \"week\",\n \"across\",\n \"market\",\n \"they\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"lmclaughlin\",\n \"timestamp\": \"2005-02-11T13:11:29.129834\"\n },\n {\n \"action\": \"created\",\n \"by\": \"verickson\",\n \"timestamp\": \"2002-03-12T22:49:54.265695\"\n },\n {\n \"action\": \"created\",\n \"by\": \"hwilliams\",\n \"timestamp\": \"1980-12-27T10:13:52.544021\"\n }\n ]\n}",
"output": "Approach:\n1. Analyze the input JSON structure: It represents a dictionary with 5 root fields (endpoint, method, responses...) 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<api_specification>\n<endpoint>/api/v1/users</endpoint>\n<method>GET</method>\n<responses>\n<_200>OK</_200>\n</responses>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.057559</generated_at>\n<version>v3.0</version>\n<tags>respond</tags>\n<tags>week</tags>\n<tags>across</tags>\n<tags>market</tags>\n<tags>they</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>lmclaughlin</by>\n<timestamp>2005-02-11T13:11:29.129834</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>verickson</by>\n<timestamp>2002-03-12T22:49:54.265695</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>hwilliams</by>\n<timestamp>1980-12-27T10:13:52.544021</timestamp>\n</audit_log>\n</api_specification>",
"estimated_tokens": 330
} |
[
{
"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 error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema: The ... | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"prompt": "Create a XML representation of error log.",
"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:06.930290</timestamp>\n<level>ERROR</level>\n<message>Budget want soldier voice.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.930580</generated_at>\n<version>v4.0</version>\n<tags>center</tags>\n<tags>coach</tags>\n<tags>marriage</tags>\n<tags>war</tags>\n<tags>end</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>psmith</by>\n<timestamp>2013-07-21T15:01:51.412630</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>justinflowers</by>\n<timestamp>2015-08-14T21:53:57.794296</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>thomasanderson</by>\n<timestamp>1988-03-19T00:39:14.076112</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 324
} |
[
{
"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:\nperiod = \"Q1\"\nsales = 936\nregion = \"Hayeston\"\n[[audit_log]]\naction = \"created\"\nb... | {
"format": "csv",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"prompt": "Transform this data from TOML to CSV:\nperiod = \"Q1\"\nsales = 936\nregion = \"Hayeston\"\n[[audit_log]]\naction = \"created\"\nby = \"gonzaleznicole\"\ntimestamp = \"1986-09-21T23:47:32.058050\"\n\n[[audit_log]]\naction = \"created\"\nby = \"kathycopeland\"\ntimestamp = \"2004-06-24T13:32:22.284076\"\n\n[[audit_log]]\naction = \"created\"\nby = \"kolsen\"\ntimestamp = \"2005-12-25T13:16:21.575744\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:06.672988\"\nversion = \"v1.0\"\ntags = [ \"hope\", \"old\", \"executive\", \"maintain\", \"result\",]\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 5 root fields (period, sales, region...) 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:\nperiod,sales,region,meta_info.generated_at,meta_info.version,meta_info.tags,audit_log\r\nQ1,936,Hayeston,2026-01-22T04:03:06.672988,v1.0,\"[\"\"hope\"\", \"\"old\"\", \"\"executive\"\", \"\"maintain\"\", \"\"result\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"gonzaleznicole\"\", \"\"timestamp\"\": \"\"1986-09-21T23:47:32.058050\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"kathycopeland\"\", \"\"timestamp\"\": \"\"2004-06-24T13:32:22.284076\"\"}, {\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"kolsen\"\", \"\"timestamp\"\": \"\"2005-12-25T13:16:21.575744\"\"}]\"\r\n",
"estimated_tokens": 272
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the YAML below into XML:\ntimestamp: '2026-01-22T04:03:05.919599'\nlevel: ERROR\nmessage: Lot street once offer get.\nmet... | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"prompt": "Reformat the YAML below into XML:\ntimestamp: '2026-01-22T04:03:05.919599'\nlevel: ERROR\nmessage: Lot street once offer get.\nmeta_info:\n generated_at: '2026-01-22T04:03:05.919736'\n version: v4.0\n tags:\n - nothing\n - such\n - recognize\n - station\n - expect\naudit_log:\n- action: created\n by: mcdaniellindsey\n timestamp: '2014-01-28T23:04:20.463910'\n- action: created\n by: coxjacqueline\n timestamp: '1976-09-29T21:37:17.011882'\n- action: created\n by: veronicamitchell\n timestamp: '1972-08-20T03:50:50.975047'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (timestamp, level, message...) 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<error_log>\n<timestamp>2026-01-22T04:03:05.919599</timestamp>\n<level>ERROR</level>\n<message>Lot street once offer get.</message>\n<meta_info>\n<generated_at>2026-01-22T04:03:05.919736</generated_at>\n<version>v4.0</version>\n<tags>nothing</tags>\n<tags>such</tags>\n<tags>recognize</tags>\n<tags>station</tags>\n<tags>expect</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>mcdaniellindsey</by>\n<timestamp>2014-01-28T23:04:20.463910</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>coxjacqueline</by>\n<timestamp>1976-09-29T21:37:17.011882</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>veronicamitchell</by>\n<timestamp>1972-08-20T03:50:50.975047</timestamp>\n</audit_log>\n</error_log>",
"estimated_tokens": 336
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate student assessment data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "xml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"prompt": "Generate student assessment data in XML format.",
"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: XML is chosen. Map dictionary keys to tags. Handle list items by repeating child tags.\n3. Generate realistic content: Use plausible names, dates, and values appropriate for the domain.\n4. Structure the data: Organize the fields logically with appropriate nesting and hierarchies.\n5. Serialize: Output the final string making sure to escape special characters if necessary.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<student>Miranda Mcdaniel</student>\n<score>32</score>\n<grade>C</grade>\n</student_assessment>",
"estimated_tokens": 177
} |
[
{
"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 JSON to TOML:\n{\n \"rx\": \"dc01f4e9-5513-47ea-b39d-bf52cafcb6e6\",\n \"drug\": \"view\",\n \"dosage\"... | {
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"prompt": "Convert the following JSON to TOML:\n{\n \"rx\": \"dc01f4e9-5513-47ea-b39d-bf52cafcb6e6\",\n \"drug\": \"view\",\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: 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 = \"dc01f4e9-5513-47ea-b39d-bf52cafcb6e6\"\ndrug = \"view\"\ndosage = \"10mg\"\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": "Output structured data for student_assessment using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Defin... | {
"format": "toml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"prompt": "Output structured data for student_assessment using TOML.",
"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: 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:\nstudent = \"Kelly Tucker\"\nscore = 82\ngrade = \"B\"\n",
"estimated_tokens": 147
} |
[
{
"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": "medium",
"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 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 XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the YAML below into XML:\nstudent: Jason Rollins\nscore: 78\ngrade: A\nmeta_info:\n generated_at: '2026-01-22T04:03:06.3... | {
"format": "xml",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"prompt": "Reformat the YAML below into XML:\nstudent: Jason Rollins\nscore: 78\ngrade: A\nmeta_info:\n generated_at: '2026-01-22T04:03:06.313130'\n version: v2.0\n tags:\n - conference\n - evening\n - industry\n - do\n - response\naudit_log:\n- action: created\n by: james96\n timestamp: '1976-06-05T22:43:59.609913'\n- action: created\n by: mooremichelle\n timestamp: '1973-07-12T04:55:15.344310'\n- action: created\n by: ashley27\n timestamp: '1987-11-06T07:10:25.924319'\n",
"output": "Approach:\n1. Analyze the input YAML structure: It represents a dictionary with 5 root fields (student, score, grade...) 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<student_assessment>\n<student>Jason Rollins</student>\n<score>78</score>\n<grade>A</grade>\n<meta_info>\n<generated_at>2026-01-22T04:03:06.313130</generated_at>\n<version>v2.0</version>\n<tags>conference</tags>\n<tags>evening</tags>\n<tags>industry</tags>\n<tags>do</tags>\n<tags>response</tags>\n</meta_info>\n<audit_log>\n<action>created</action>\n<by>james96</by>\n<timestamp>1976-06-05T22:43:59.609913</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>mooremichelle</by>\n<timestamp>1973-07-12T04:55:15.344310</timestamp>\n</audit_log>\n<audit_log>\n<action>created</action>\n<by>ashley27</by>\n<timestamp>1987-11-06T07:10:25.924319</timestamp>\n</audit_log>\n</student_assessment>",
"estimated_tokens": 324
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate research paper data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"prompt": "Generate research paper data in TOML format.",
"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.12464\"\ntitle = \"Organic hybrid time-frame\"\nabstract = \"Game bad inside young simple. Result more service. Learn fine fast establish from purpose.\\nMoment total serious suggest always tax.\"\nkeywords = [ \"live\", \"sport\", \"prevent\", \"offer\",]\n[[authors]]\nname = \"Johnny Thomas\"\naffiliation = \"Collins, Kim and Sexton\"\nemail = \"[email protected]\"\n\n[[authors]]\nname = \"Joseph Hansen\"\naffiliation = \"Clements LLC\"\nemail = \"[email protected]\"\n\n[[authors]]\nname = \"Parker Mullen\"\naffiliation = \"Johnson-Watson\"\nemail = \"[email protected]\"\n\n[[authors]]\nname = \"Patrick Gaines\"\naffiliation = \"Scott, Parks and Torres\"\nemail = \"[email protected]\"\n\n[publication]\nvenue = \"ICLR\"\nyear = 2021\ndoi = \"10.8155/HVNG\"\n",
"estimated_tokens": 319
} |
[
{
"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 sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the sch... | {
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"prompt": "Create a JSON representation of sales analytics.",
"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: 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 \"period\": \"Q1\",\n \"sales\": 3795,\n \"region\": \"East Travishaven\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.381605\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"eight\",\n \"her\",\n \"mean\",\n \"nation\",\n \"theory\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"blackstephen\",\n \"timestamp\": \"1992-08-29T14:58:22.613839\"\n }\n ]\n}",
"estimated_tokens": 236
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate course syllabus data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema... | {
"format": "toml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"prompt": "Generate course syllabus data in TOML format.",
"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: 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:\ncourse = \"Customer-focused heuristic toolset\"\nweeks = 12\ncredits = 3\n[[audit_log]]\naction = \"created\"\nby = \"rochamichael\"\ntimestamp = \"2011-03-20T22:35:12.834387\"\n\n[[audit_log]]\naction = \"created\"\nby = \"pray\"\ntimestamp = \"2021-05-21T15:12:16.651042\"\n\n[meta_info]\ngenerated_at = \"2026-01-22T04:03:07.050026\"\nversion = \"v3.0\"\ntags = [ \"cut\", \"result\", \"campaign\", \"network\", \"make\",]\n",
"estimated_tokens": 231
} |
[
{
"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\nPm meet type.,\"Left family agency tend necessary floor. Shake budget care lose.\nNewspaper choice never perhaps rather. Boy where source condition. Their opportunity lay standard in their clear mother.\",Lauren Robbins,2026-01-22T04:03:05.270016,v3.0,\"[\"\"western\"\", \"\"lose\"\", \"\"find\"\", \"\"let\"\", \"\"which\"\"]\",\"[{\"\"action\"\": \"\"created\"\", \"\"by\"\": \"\"fisherkimberly\"\", \"\"timestamp\"\": \"\"1996-09-22T05:33:10.328896\"\"}]\"\r\n",
"estimated_tokens": 266
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the TOML below into XML:\ntxn = \"84ee87a6-9fc0-406b-aaa9-04fb2e2835df\"\namount = 364.43\nstatus = \"completed\"\n"
},... | {
"format": "xml",
"complexity": "medium",
"schema": "transaction_record",
"type": "conversion",
"prompt": "Reformat the TOML below into XML:\ntxn = \"84ee87a6-9fc0-406b-aaa9-04fb2e2835df\"\namount = 364.43\nstatus = \"completed\"\n",
"output": "Approach:\n1. Analyze the input TOML structure: It represents a dictionary with 3 root fields (txn, amount, status) 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<transaction_record>\n<txn>84ee87a6-9fc0-406b-aaa9-04fb2e2835df</txn>\n<amount>364.43</amount>\n<status>completed</status>\n</transaction_record>",
"estimated_tokens": 188
} |
[
{
"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": "medium",
"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 3 root fields (user, post, likes) 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: heidi64\npost: 'Give TV town important sell have. Gas pattern face away trip. Its out order.\n\n Wrong front pick every management. Partner car big.'\nlikes: 168\n",
"estimated_tokens": 178
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the ... | {
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"prompt": "Create a JSON representation of student assessment.",
"output": "Approach:\n1. Define the schema: The student_assessment should contain a dictionary with 5 root fields (student, score, grade...) and a nesting depth of 3.\n2. Select the format: 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 \"student\": \"Scott Avery\",\n \"score\": 31,\n \"grade\": \"C\",\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:05.179661\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"data\",\n \"sort\",\n \"world\",\n \"notice\",\n \"foot\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"angie36\",\n \"timestamp\": \"2002-01-29T16:21:09.968726\"\n },\n {\n \"action\": \"created\",\n \"by\": \"myersdustin\",\n \"timestamp\": \"1983-06-28T20:59:32.361167\"\n },\n {\n \"action\": \"created\",\n \"by\": \"michaelking\",\n \"timestamp\": \"2019-04-24T00:16:41.731738\"\n }\n ]\n}",
"estimated_tokens": 291
} |
[
{
"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": "medium",
"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 3 root fields (product, price, stock) 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:\nproduct,price,stock\r\nfill,38.15,30\r\n",
"estimated_tokens": 150
} |
[
{
"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 customer_review using TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "toml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Output structured data for customer_review using TOML.",
"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: 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 = \"garciashelly\"\nrating = 3\ncomment = \"Commercial wall factor Congress.\"\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": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<timestamp>2026-01-22T04:03:05.171337</... | {
"format": "csv",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"prompt": "Reformat the XML below into CSV:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<timestamp>2026-01-22T04:03:05.171337</timestamp>\n<level>ERROR</level>\n<message>Public skin compare tough level.</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: 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:\ntimestamp,level,message\r\n2026-01-22T04:03:05.171337,ERROR,Public skin compare tough level.\r\n",
"estimated_tokens": 171
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Analyze the data structure and generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate social media post data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Define the schema:... | {
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"prompt": "Generate social media post data in XML format.",
"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>cannonjennifer</user>\n<post>Dark event poor effect including rise.</post>\n<likes>799</likes>\n</social_media_post>",
"estimated_tokens": 182
} |
[
{
"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": "complex",
"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 5 root fields (product, price, stock...) 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 \"product\": \"hand\",\n \"price\": 91.15,\n \"stock\": 34,\n \"meta_info\": {\n \"generated_at\": \"2026-01-22T04:03:07.234460\",\n \"version\": \"v2.0\",\n \"tags\": [\n \"address\",\n \"field\",\n \"young\",\n \"herself\",\n \"real\"\n ]\n },\n \"audit_log\": [\n {\n \"action\": \"created\",\n \"by\": \"kelly75\",\n \"timestamp\": \"1992-05-22T05:33:39.572839\"\n },\n {\n \"action\": \"created\",\n \"by\": \"egraham\",\n \"timestamp\": \"2013-10-06T03:20:54.157050\"\n }\n ]\n}",
"estimated_tokens": 260
} |
[
{
"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": "simple",
"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 4 root fields (experiment_id, title, metrics...) 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:\nexperiment_id,title,metrics.accuracy,metrics.loss,metrics.epoch,config.batch_size,config.optimizer,config.lr\r\nEXP-481272,Analysis of production,0.9889,0.3569,46,128,adam,0.001\r\n",
"estimated_tokens": 188
} |
[
{
"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 customer_review using YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Define t... | {
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"prompt": "Output structured data for customer_review using YAML.",
"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: garciashelly\nrating: 3\ncomment: Commercial wall factor Congress.\n",
"estimated_tokens": 155
} |
[
{
"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 \"user\": \"shayes\",\n \"post\": \"Look add civil. Keep also job book play many. ... | {
"format": "yaml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"prompt": "Transform this data from JSON to YAML:\n{\n \"user\": \"shayes\",\n \"post\": \"Look add civil. Keep also job book play many. Network notice husband public every card.\",\n \"likes\": 572\n}",
"output": "Approach:\n1. Analyze the input JSON 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: shayes\npost: Look add civil. Keep also job book play many. Network notice husband public\n every card.\nlikes: 572\n",
"estimated_tokens": 172
} |
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.