naoyasss/qwen3-4b-structured-output-lora_rev0.7
Text Generation
•
Updated
•
7
messages
listlengths 3
3
| metadata
dict | assistant
stringlengths 44
1.68k
|
|---|---|---|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Transform this CSV data into TOML format:\nassessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type\r\nASMT-554535,,CRS-9992,,2026-01-03,B,,,,,63.99,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 9, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 6, \"\"po\",STU-693793,,,86,exam\r\n,TNY218,CRS-7794,4,,,40,30,30,Kara Bennett,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"present\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"arrive\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"school\"\"}, {\"\"\",,,Spring 2023,Monitored mobile analyzer 101,,\r\n,ZDW419,CRS-8967,3,,,40,30,30,Cheryl Downs,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"form\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"important\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"enter\"\"}, {\"\"w\",,,Spring 2022,Profit-focused intangible neural-net 101,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from CSV to TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nassessment_id = \"ASMT-554535\"\nstudent_id = \"STU-693793\"\ncourse_id = \"CRS-9992\"\ntype = \"exam\"\ndate = \"2026-01-03\"\ntotal_score = 86\npercentage = 63.99\ngrade = \"B\"\n[[scores]]\nquestion = 1\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 7\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 8\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 3\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 276
}
|
assessment_id = "ASMT-554535"
student_id = "STU-693793"
course_id = "CRS-9992"
type = "exam"
date = "2026-01-03"
total_score = 86
percentage = 63.99
grade = "B"
[[scores]]
question = 1
points_earned = 9
points_possible = 10
[[scores]]
question = 2
points_earned = 6
points_possible = 10
[[scores]]
question = 3
points_earned = 7
points_possible = 10
[[scores]]
question = 4
points_earned = 6
points_possible = 10
[[scores]]
question = 5
points_earned = 6
points_possible = 10
[[scores]]
question = 6
points_earned = 1
points_possible = 10
[[scores]]
question = 7
points_earned = 4
points_possible = 10
[[scores]]
question = 8
points_earned = 8
points_possible = 10
[[scores]]
question = 9
points_earned = 2
points_possible = 10
[[scores]]
question = 10
points_earned = 3
points_possible = 10
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"review_id\": \"REV-1521978\",\n \"product_id\": \"PROD-894495\",\n \"user_id\": \"0e93d4dc-0d39-4af2-8ec3-d8d1250011b9\",\n \"rating\": 4,\n \"title\": \"Great how data open such.\",\n \"content\": \"City not either situation all along might. Under could expect build member. Fish ready onto white majority.\",\n \"date\": \"2026-01-05\",\n \"verified_purchase\": false,\n \"helpful_votes\": 57\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-1521978</review_id>\n<product_id>PROD-894495</product_id>\n<user_id>0e93d4dc-0d39-4af2-8ec3-d8d1250011b9</user_id>\n<rating>4</rating>\n<title>Great how data open such.</title>\n<content>City not either situation all along might. Under could expect build member. Fish ready onto white majority.</content>\n<date>2026-01-05</date>\n<verified_purchase>False</verified_purchase>\n<helpful_votes>57</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 202
}
|
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-1521978</review_id>
<product_id>PROD-894495</product_id>
<user_id>0e93d4dc-0d39-4af2-8ec3-d8d1250011b9</user_id>
<rating>4</rating>
<title>Great how data open such.</title>
<content>City not either situation all along might. Under could expect build member. Fish ready onto white majority.</content>
<date>2026-01-05</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>57</helpful_votes>
</customer_review>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output lab result as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id = \"LAB-8093004\"\npatient_mrn = \"MRN-777027\"\norder_date = \"2026-01-05\"\npanel = \"CMP\"\n[[results]]\ntest = \"Glucose\"\nvalue = 140.2\nunit = \"mg/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 96.3\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 185.0\nunit = \"g/dL\"\nflag = \"high\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 139.7\nunit = \"g/dL\"\nflag = \"low\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 169
}
|
result_id = "LAB-8093004"
patient_mrn = "MRN-777027"
order_date = "2026-01-05"
panel = "CMP"
[[results]]
test = "Glucose"
value = 140.2
unit = "mg/dL"
flag = "low"
[[results]]
test = "Hemoglobin"
value = 96.3
unit = "g/dL"
flag = "normal"
[[results]]
test = "Glucose"
value = 185.0
unit = "g/dL"
flag = "high"
[[results]]
test = "Glucose"
value = 139.7
unit = "g/dL"
flag = "low"
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate lab result data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"result_id\": \"LAB-3793814\",\n \"patient_mrn\": \"MRN-247204\",\n \"order_date\": \"2026-01-03\",\n \"panel\": \"CBC\",\n \"results\": [\n {\n \"test\": \"Hemoglobin\",\n \"value\": 188.2,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 197.7,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 196.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 193.9,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 197.2,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 109.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"normal\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 265
}
|
{
"result_id": "LAB-3793814",
"patient_mrn": "MRN-247204",
"order_date": "2026-01-03",
"panel": "CBC",
"results": [
{
"test": "Hemoglobin",
"value": 188.2,
"unit": "g/dL",
"flag": "low"
},
{
"test": "WBC",
"value": 197.7,
"unit": "mg/dL",
"flag": "high"
},
{
"test": "Glucose",
"value": 196.4,
"unit": "mg/dL",
"flag": "high"
},
{
"test": "Glucose",
"value": 193.9,
"unit": "g/dL",
"flag": "high"
},
{
"test": "Glucose",
"value": 197.2,
"unit": "g/dL",
"flag": "low"
},
{
"test": "Hemoglobin",
"value": 109.5,
"unit": "mg/dL",
"flag": "normal"
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Create a XML representation of customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-5008217</review_id>\n<product_id>PROD-173271</product_id>\n<user_id>11121b86-b60c-4ea2-b83a-cbb727cd7a24</user_id>\n<rating>2</rating>\n<title>Lay lead it politics brother.</title>\n<content>Camera left hope prevent inside real. Whether trouble their always manager cultural majority popular. Song condition entire security concern science. Run number firm listen serious.</content>\n<date>2026-01-01</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>23</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 219
}
|
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-5008217</review_id>
<product_id>PROD-173271</product_id>
<user_id>11121b86-b60c-4ea2-b83a-cbb727cd7a24</user_id>
<rating>2</rating>
<title>Lay lead it politics brother.</title>
<content>Camera left hope prevent inside real. Whether trouble their always manager cultural majority popular. Song condition entire security concern science. Run number firm listen serious.</content>
<date>2026-01-01</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>23</helpful_votes>
</customer_review>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate clinical note data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nnote_id: CN-7937835\npatient:\n mrn: MRN-749785\n age: 66\n gender: M\nencounter_date: '2026-01-06'\nchief_complaint: chest pain\nvitals:\n bp: 179/85\n hr: 81\n temp_f: 101.7\nassessment:\n- problem: hypertension\n icd10: I52\n- problem: diabetes\n icd10: J76\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 140
}
|
note_id: CN-7937835
patient:
mrn: MRN-749785
age: 66
gender: M
encounter_date: '2026-01-06'
chief_complaint: chest pain
vitals:
bp: 179/85
hr: 81
temp_f: 101.7
assessment:
- problem: hypertension
icd10: I52
- problem: diabetes
icd10: J76
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>January 2022</period>\n<total_revenue>7456708</total_revenue>\n<units_sold>82349</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>3622404</revenue>\n<growth>-8.05</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>1893923</revenue>\n<growth>2.21</growth>\n</channels>\n<top_products>\n<sku>SKU-2073</sku>\n<sales>98550</sales>\n</top_products>\n<top_products>\n<sku>SKU-3707</sku>\n<sales>233488</sales>\n</top_products>\n<top_products>\n<sku>SKU-7843</sku>\n<sales>172526</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 222
}
|
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>January 2022</period>
<total_revenue>7456708</total_revenue>
<units_sold>82349</units_sold>
<channels>
<name>wholesale</name>
<revenue>3622404</revenue>
<growth>-8.05</growth>
</channels>
<channels>
<name>online</name>
<revenue>1893923</revenue>
<growth>2.21</growth>
</channels>
<top_products>
<sku>SKU-2073</sku>
<sales>98550</sales>
</top_products>
<top_products>
<sku>SKU-3707</sku>
<sales>233488</sales>
</top_products>
<top_products>
<sku>SKU-7843</sku>
<sales>172526</sales>
</top_products>
</sales_analytics>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\narticle_id,author,content,headline,published,section,shares,tags,views\r\nART-8172649,Rachel Clark,\"Pattern capital time compare include night top. Large than important morning.\nCard authority protect\",Triple-buffered responsive model,2026-01-03T00:35:22.551008,Business,392,\"[\"\"consider\"\", \"\"whatever\"\", \"\"part\"\", \"\"however\"\", \"\"special\"\"]\",49705\r\nART-1645366,Amanda Martinez,\"Crime establish ahead program speech child. Contain reveal ahead fire capital necessary.\nSuggest tow\",Enterprise-wide reciprocal application,2026-01-01T21:09:16.034149,Business,1537,\"[\"\"season\"\", \"\"site\"\", \"\"political\"\", \"\"loss\"\", \"\"chair\"\"]\",98841\r\nART-5999482,Dennis Allen,\"Not way heart decision. Product seven into here girl argue. Free effect central everything white.\nPo\",Monitored 24/7 budgetary management,2026-01-05T03:19:57.275932,Politics,784,\"[\"\"mouth\"\", \"\"maintain\"\", \"\"establish\"\"]\",86058\r\nART-4000273,Austin Jones,Consider probably show when grow opportunity. Lay find relationship realize give. Ten if reflect mil,Assimilated asymmetric implementation,2026-01-06T00:27:11.144144,Tech,109,\"[\"\"benefit\"\", \"\"song\"\", \"\"vote\"\", \"\"long\"\", \"\"commercial\"\"]\",10210\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\narticle_id: ART-8172649\nheadline: Triple-buffered responsive model\nauthor: Rachel Clark\npublished: '2026-01-03T00:35:22.551008'\nsection: Business\ncontent: 'Pattern capital time compare include night top. Large than important morning.\n\n Card authority protect present return while middle. Development miss write five.'\ntags:\n- consider\n- whatever\n- part\n- however\n- special\nviews: 49705\nshares: 392\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 178
}
|
article_id: ART-8172649
headline: Triple-buffered responsive model
author: Rachel Clark
published: '2026-01-03T00:35:22.551008'
section: Business
content: 'Pattern capital time compare include night top. Large than important morning.
Card authority protect present return while middle. Development miss write five.'
tags:
- consider
- whatever
- part
- however
- special
views: 49705
shares: 392
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment_id = \"ASMT-948175\"\nstudent_id = \"STU-160858\"\ncourse_id = \"CRS-5368\"\ntype = \"assignment\"\ndate = \"2026-01-03\"\ntotal_score = 89\npercentage = 96.29\ngrade = \"B\"\n[[scores]]\nquestion = 1\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 9\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 261
}
|
assessment_id = "ASMT-948175"
student_id = "STU-160858"
course_id = "CRS-5368"
type = "assignment"
date = "2026-01-03"
total_score = 89
percentage = 96.29
grade = "B"
[[scores]]
question = 1
points_earned = 1
points_possible = 10
[[scores]]
question = 2
points_earned = 9
points_possible = 10
[[scores]]
question = 3
points_earned = 2
points_possible = 10
[[scores]]
question = 4
points_earned = 9
points_possible = 10
[[scores]]
question = 5
points_earned = 5
points_possible = 10
[[scores]]
question = 6
points_earned = 9
points_possible = 10
[[scores]]
question = 7
points_earned = 1
points_possible = 10
[[scores]]
question = 8
points_earned = 3
points_possible = 10
[[scores]]
question = 9
points_earned = 9
points_possible = 10
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output social media post as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"post_id\": \"POST-52722833\",\n \"platform\": \"facebook\",\n \"user_id\": \"d42576ea-a78d-4261-852d-cbcc2fd55da5\",\n \"username\": \"justin96\",\n \"content\": \"Southern write three operation throw interest whether.\\nDecade quality training employee. Financial out position catch finish author. Past over in create.\\nNice reduce try contain future back customer.\",\n \"timestamp\": \"2026-01-07T13:51:26.716888\",\n \"hashtags\": [\n \"#report\",\n \"#newspaper\"\n ],\n \"engagement\": {\n \"likes\": 8106,\n \"shares\": 850,\n \"comments\": 244\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 211
}
|
{
"post_id": "POST-52722833",
"platform": "facebook",
"user_id": "d42576ea-a78d-4261-852d-cbcc2fd55da5",
"username": "justin96",
"content": "Southern write three operation throw interest whether.\nDecade quality training employee. Financial out position catch finish author. Past over in create.\nNice reduce try contain future back customer.",
"timestamp": "2026-01-07T13:51:26.716888",
"hashtags": [
"#report",
"#newspaper"
],
"engagement": {
"likes": 8106,
"shares": 850,
"comments": 244
}
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<research_paper>\n<paper_id>arXiv:2024.31964</paper_id>\n<title>Optimized solution-oriented success</title>\n<authors>\n<name>Meagan Sutton</name>\n<affiliation>Williamson, Mitchell and Smith</affiliation>\n<email>davilabridget@example.com</email>\n</authors>\n<authors>\n<name>William Gross</name>\n<affiliation>Miller and Sons</affiliation>\n<email>linda03@example.net</email>\n</authors>\n<abstract>Price while never. Night great must well remain. Share less reveal often.</abstract>\n<keywords>less</keywords>\n<keywords>radio</keywords>\n<keywords>spend</keywords>\n<keywords>which</keywords>\n<publication>\n<venue>Science</venue>\n<year>2023</year>\n<doi>10.4651/vEqE</doi>\n</publication>\n<citations>155</citations>\n<funding_source />\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"paper_id\": \"arXiv:2024.31964\",\n \"title\": \"Optimized solution-oriented success\",\n \"authors\": [\n {\n \"name\": \"Meagan Sutton\",\n \"affiliation\": \"Williamson, Mitchell and Smith\",\n \"email\": \"davilabridget@example.com\"\n },\n {\n \"name\": \"William Gross\",\n \"affiliation\": \"Miller and Sons\",\n \"email\": \"linda03@example.net\"\n }\n ],\n \"abstract\": \"Price while never. Night great must well remain. Share less reveal often.\",\n \"keywords\": [\n \"less\",\n \"radio\",\n \"spend\",\n \"which\"\n ],\n \"publication\": {\n \"venue\": \"Science\",\n \"year\": 2023,\n \"doi\": \"10.4651/vEqE\"\n },\n \"citations\": 155,\n \"funding_source\": null\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 246
}
|
{
"paper_id": "arXiv:2024.31964",
"title": "Optimized solution-oriented success",
"authors": [
{
"name": "Meagan Sutton",
"affiliation": "Williamson, Mitchell and Smith",
"email": "davilabridget@example.com"
},
{
"name": "William Gross",
"affiliation": "Miller and Sons",
"email": "linda03@example.net"
}
],
"abstract": "Price while never. Night great must well remain. Share less reveal often.",
"keywords": [
"less",
"radio",
"spend",
"which"
],
"publication": {
"venue": "Science",
"year": 2023,
"doi": "10.4651/vEqE"
},
"citations": 155,
"funding_source": null
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a lab result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<result_id>LAB-1056021</result_id>\n<patient_mrn>MRN-977601</patient_mrn>\n<order_date>2026-01-02</order_date>\n<panel>CMP</panel>\n<results>\n<test>WBC</test>\n<value>124.0</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>114.5</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>70.6</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>119.6</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>171.0</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n</lab_result>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 248
}
|
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-1056021</result_id>
<patient_mrn>MRN-977601</patient_mrn>
<order_date>2026-01-02</order_date>
<panel>CMP</panel>
<results>
<test>WBC</test>
<value>124.0</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>114.5</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>WBC</test>
<value>70.6</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>119.6</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>171.0</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"experiment_id\": \"EXP-139463\",\n \"title\": \"Effect of quite on arm\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 371,\n \"duration_days\": 284\n },\n \"results\": [\n {\n \"metric\": \"safety\",\n \"baseline\": 91.61,\n \"endpoint\": 76.9,\n \"p_value\": 0.4003\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 58.96,\n \"endpoint\": 23.83,\n \"p_value\": 0.3437\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 23.31,\n \"endpoint\": 88.63,\n \"p_value\": 0.3018\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<experiment_id>EXP-139463</experiment_id>\n<title>Effect of quite on arm</title>\n<methodology>\n<design>RCT</design>\n<sample_size>371</sample_size>\n<duration_days>284</duration_days>\n</methodology>\n<results>\n<metric>safety</metric>\n<baseline>91.61</baseline>\n<endpoint>76.9</endpoint>\n<p_value>0.4003</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>58.96</baseline>\n<endpoint>23.83</endpoint>\n<p_value>0.3437</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>23.31</baseline>\n<endpoint>88.63</endpoint>\n<p_value>0.3018</p_value>\n</results>\n<conclusion>non-significant</conclusion>\n</experiment_result>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 251
}
|
<?xml version="1.0" encoding="UTF-8"?>
<experiment_result>
<experiment_id>EXP-139463</experiment_id>
<title>Effect of quite on arm</title>
<methodology>
<design>RCT</design>
<sample_size>371</sample_size>
<duration_days>284</duration_days>
</methodology>
<results>
<metric>safety</metric>
<baseline>91.61</baseline>
<endpoint>76.9</endpoint>
<p_value>0.4003</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>58.96</baseline>
<endpoint>23.83</endpoint>
<p_value>0.3437</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>23.31</baseline>
<endpoint>88.63</endpoint>
<p_value>0.3018</p_value>
</results>
<conclusion>non-significant</conclusion>
</experiment_result>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<level>ERROR</level>\n<service>writeService</service>\n<error_id>85223c4c-4b76-4351-95ee-55a2460043f3</error_id>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"level\": \"ERROR\",\n \"service\": \"writeService\",\n \"error_id\": \"85223c4c-4b76-4351-95ee-55a2460043f3\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 105
}
|
{
"level": "ERROR",
"service": "writeService",
"error_id": "85223c4c-4b76-4351-95ee-55a2460043f3"
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntitle: Stand-alone empowering functionalities 101\nschedule:\n- week: 1\n topic: class\n- week: 2\n topic: leave\n- week: 3\n topic: develop\n- week: 4\n topic: style\n- week: 5\n topic: again\n- week: 6\n topic: man\n- week: 7\n topic: list\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 150
}
|
title: Stand-alone empowering functionalities 101
schedule:
- week: 1
topic: class
- week: 2
topic: leave
- week: 3
topic: develop
- week: 4
topic: style
- week: 5
topic: again
- week: 6
topic: man
- week: 7
topic: list
grading:
homework: 30
midterm: 30
final: 40
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-469887\",\n \"is_available\": true,\n \"reviews\": 612,\n \"name\": \"Networked executive capability\",\n \"currency\": \"USD\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 114
}
|
{
"product_id": "PROD-469887",
"is_available": true,
"reviews": 612,
"name": "Networked executive capability",
"currency": "USD"
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following CSV to YAML:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nGDK183,CRS-6873,3,40,30,30,Melinda Thompson,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"girl\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"explain\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"center\"\"}, {\"\"we\",Fall 2020,Grass-roots 24/7 emulation 101\r\nUWL437,CRS-9225,4,40,30,30,Monica Stewart,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"Democrat\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"clearly\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"sign\"\"}, {\"\"\",Fall 2024,Balanced interactive initiative 101\r\nRFE382,CRS-4501,4,40,30,30,Ryan Morris DDS,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"address\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"democratic\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"least\"\"},\",Fall 2023,Persistent next generation superstructure 101\r\nRLJ212,CRS-9484,4,40,30,30,Lisa Blevins,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"join\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"safe\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"we\"\"}, {\"\"week\"\": 4,\",Spring 2023,De-engineered transitional functionalities 101\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from CSV to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ncourse_id: CRS-6873\ncode: GDK183\ntitle: Grass-roots 24/7 emulation 101\ninstructor: Melinda Thompson\ncredits: 3\nterm: Fall 2020\nschedule:\n- week: 1\n topic: girl\n- week: 2\n topic: explain\n- week: 3\n topic: center\n- week: 4\n topic: almost\n- week: 5\n topic: property\n- week: 6\n topic: call\n- week: 7\n topic: bad\n- week: 8\n topic: study\n- week: 9\n topic: campaign\n- week: 10\n topic: performance\n- week: 11\n topic: sport\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 198
}
|
course_id: CRS-6873
code: GDK183
title: Grass-roots 24/7 emulation 101
instructor: Melinda Thompson
credits: 3
term: Fall 2020
schedule:
- week: 1
topic: girl
- week: 2
topic: explain
- week: 3
topic: center
- week: 4
topic: almost
- week: 5
topic: property
- week: 6
topic: call
- week: 7
topic: bad
- week: 8
topic: study
- week: 9
topic: campaign
- week: 10
topic: performance
- week: 11
topic: sport
grading:
homework: 30
midterm: 30
final: 40
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"February 2020\",\n \"total_revenue\": 2007174,\n \"units_sold\": 24558,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 235807,\n \"growth\": 46.03\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 4419318,\n \"growth\": 24.35\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6554\",\n \"sales\": 258652\n },\n {\n \"sku\": \"SKU-8652\",\n \"sales\": 200091\n },\n {\n \"sku\": \"SKU-9581\",\n \"sales\": 65110\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 197
}
|
{
"period": "February 2020",
"total_revenue": 2007174,
"units_sold": 24558,
"channels": [
{
"name": "online",
"revenue": 235807,
"growth": 46.03
},
{
"name": "wholesale",
"revenue": 4419318,
"growth": 24.35
}
],
"top_products": [
{
"sku": "SKU-6554",
"sales": 258652
},
{
"sku": "SKU-8652",
"sales": 200091
},
{
"sku": "SKU-9581",
"sales": 65110
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate sales analytics data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>May 2020</period>\n<total_revenue>9864225</total_revenue>\n<units_sold>74086</units_sold>\n<channels>\n<name>online</name>\n<revenue>906832</revenue>\n<growth>-8.93</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>2437365</revenue>\n<growth>2.73</growth>\n</channels>\n<top_products>\n<sku>SKU-7032</sku>\n<sales>420063</sales>\n</top_products>\n<top_products>\n<sku>SKU-9360</sku>\n<sales>149398</sales>\n</top_products>\n<top_products>\n<sku>SKU-9440</sku>\n<sales>105905</sales>\n</top_products>\n</sales_analytics>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 222
}
|
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>May 2020</period>
<total_revenue>9864225</total_revenue>
<units_sold>74086</units_sold>
<channels>
<name>online</name>
<revenue>906832</revenue>
<growth>-8.93</growth>
</channels>
<channels>
<name>wholesale</name>
<revenue>2437365</revenue>
<growth>2.73</growth>
</channels>
<top_products>
<sku>SKU-7032</sku>
<sales>420063</sales>
</top_products>
<top_products>
<sku>SKU-9360</sku>
<sales>149398</sales>
</top_products>
<top_products>
<sku>SKU-9440</sku>
<sales>105905</sales>
</top_products>
</sales_analytics>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate course syllabus data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncourse_id = \"CRS-6873\"\ncode = \"GDK183\"\ntitle = \"Grass-roots 24/7 emulation 101\"\ninstructor = \"Melinda Thompson\"\ncredits = 3\nterm = \"Fall 2020\"\n[[schedule]]\nweek = 1\ntopic = \"girl\"\n\n[[schedule]]\nweek = 2\ntopic = \"explain\"\n\n[[schedule]]\nweek = 3\ntopic = \"center\"\n\n[[schedule]]\nweek = 4\ntopic = \"almost\"\n\n[[schedule]]\nweek = 5\ntopic = \"property\"\n\n[[schedule]]\nweek = 6\ntopic = \"call\"\n\n[[schedule]]\nweek = 7\ntopic = \"bad\"\n\n[[schedule]]\nweek = 8\ntopic = \"study\"\n\n[[schedule]]\nweek = 9\ntopic = \"campaign\"\n\n[[schedule]]\nweek = 10\ntopic = \"performance\"\n\n[[schedule]]\nweek = 11\ntopic = \"sport\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 232
}
|
course_id = "CRS-6873"
code = "GDK183"
title = "Grass-roots 24/7 emulation 101"
instructor = "Melinda Thompson"
credits = 3
term = "Fall 2020"
[[schedule]]
week = 1
topic = "girl"
[[schedule]]
week = 2
topic = "explain"
[[schedule]]
week = 3
topic = "center"
[[schedule]]
week = 4
topic = "almost"
[[schedule]]
week = 5
topic = "property"
[[schedule]]
week = 6
topic = "call"
[[schedule]]
week = 7
topic = "bad"
[[schedule]]
week = 8
topic = "study"
[[schedule]]
week = 9
topic = "campaign"
[[schedule]]
week = 10
topic = "performance"
[[schedule]]
week = 11
topic = "sport"
[grading]
homework = 30
midterm = 30
final = 40
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"instructor\": \"Rachel Moreno DVM\",\n \"credits\": 4,\n \"course_id\": \"CRS-8305\",\n \"title\": \"Open-architected even-keeled support 101\",\n \"term\": \"Spring 2023\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<instructor>Rachel Moreno DVM</instructor>\n<credits>4</credits>\n<course_id>CRS-8305</course_id>\n<title>Open-architected even-keeled support 101</title>\n<term>Spring 2023</term>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 143
}
|
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<instructor>Rachel Moreno DVM</instructor>
<credits>4</credits>
<course_id>CRS-8305</course_id>
<title>Open-architected even-keeled support 101</title>
<term>Spring 2023</term>
</course_syllabus>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output clinical note as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-8293808\",\n \"patient\": {\n \"mrn\": \"MRN-980604\",\n \"age\": 24,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-05\",\n \"chief_complaint\": \"fever\",\n \"vitals\": {\n \"bp\": \"150/98\",\n \"hr\": 93,\n \"temp_f\": 102.4\n },\n \"assessment\": [\n {\n \"problem\": \"diabetes\",\n \"icd10\": \"J39\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 159
}
|
{
"note_id": "CN-8293808",
"patient": {
"mrn": "MRN-980604",
"age": 24,
"gender": "F"
},
"encounter_date": "2026-01-05",
"chief_complaint": "fever",
"vitals": {
"bp": "150/98",
"hr": 93,
"temp_f": 102.4
},
"assessment": [
{
"problem": "diabetes",
"icd10": "J39"
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id = \"CTR-896633\"\neffective_date = \"2026-01-03\"\nterm_months = 21\nvalue = 926875\nstatus = \"pending\"\n[[parties]]\nname = \"Smith-Cross\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Carrillo and Sons\"\nrole = \"party_b\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 127
}
|
contract_id = "CTR-896633"
effective_date = "2026-01-03"
term_months = 21
value = 926875
status = "pending"
[[parties]]
name = "Smith-Cross"
role = "party_a"
[[parties]]
name = "Carrillo and Sons"
role = "party_b"
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Optional bottom-line complexity API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</traditional>\n<get>\n<summary>Discussion then kind hair.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//traditional>\n</paths>\n</api_specification>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Optional bottom-line complexity API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/traditional\": {\n \"get\": {\n \"summary\": \"Discussion then kind hair.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 246
}
|
{
"openapi": "3.0.0",
"info": {
"title": "Optional bottom-line complexity API",
"version": "1.0.0"
},
"paths": {
"/traditional": {
"get": {
"summary": "Discussion then kind hair.",
"parameters": [
{
"name": "param0",
"in": "query",
"type": "string"
},
{
"name": "param1",
"in": "query",
"type": "string"
}
],
"responses": {
"200": {
"description": "Success"
},
"400": {
"description": "Bad Request"
}
}
}
}
}
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"contract_id\": \"CTR-370819\",\n \"parties\": [\n {\n \"name\": \"Stewart, Thompson and Rogers\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Jackson, Griffin and Flowers\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 13,\n \"value\": 109351,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-370819</contract_id>\n<parties>\n<name>Stewart, Thompson and Rogers</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Jackson, Griffin and Flowers</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-01</effective_date>\n<term_months>13</term_months>\n<value>109351</value>\n<status>active</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 173
}
|
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-370819</contract_id>
<parties>
<name>Stewart, Thompson and Rogers</name>
<role>party_a</role>
</parties>
<parties>
<name>Jackson, Griffin and Flowers</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-01</effective_date>
<term_months>13</term_months>
<value>109351</value>
<status>active</status>
</contract>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-3766387</note_id>\n<patient>\n<mrn>MRN-378219</mrn>\n<age>48</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>145/101</bp>\n<hr>106</hr>\n<temp_f>101.7</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>J94</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 179
}
|
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-3766387</note_id>
<patient>
<mrn>MRN-378219</mrn>
<age>48</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-04</encounter_date>
<chief_complaint>headache</chief_complaint>
<vitals>
<bp>145/101</bp>
<hr>106</hr>
<temp_f>101.7</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>J94</icd10>
</assessment>
</clinical_note>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"assessment_id\": \"ASMT-744456\",\n \"student_id\": \"STU-954920\",\n \"course_id\": \"CRS-3021\",\n \"type\": \"exam\",\n \"date\": \"2026-01-03\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 1,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 9,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 97,\n \"percentage\": 89.67,\n \"grade\": \"C\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 397
}
|
{
"assessment_id": "ASMT-744456",
"student_id": "STU-954920",
"course_id": "CRS-3021",
"type": "exam",
"date": "2026-01-03",
"scores": [
{
"question": 1,
"points_earned": 7,
"points_possible": 10
},
{
"question": 2,
"points_earned": 2,
"points_possible": 10
},
{
"question": 3,
"points_earned": 2,
"points_possible": 10
},
{
"question": 4,
"points_earned": 9,
"points_possible": 10
},
{
"question": 5,
"points_earned": 5,
"points_possible": 10
},
{
"question": 6,
"points_earned": 10,
"points_possible": 10
},
{
"question": 7,
"points_earned": 5,
"points_possible": 10
},
{
"question": 8,
"points_earned": 1,
"points_possible": 10
},
{
"question": 9,
"points_earned": 9,
"points_possible": 10
},
{
"question": 10,
"points_earned": 3,
"points_possible": 10
},
{
"question": 11,
"points_earned": 9,
"points_possible": 10
},
{
"question": 12,
"points_earned": 9,
"points_possible": 10
}
],
"total_score": 97,
"percentage": 89.67,
"grade": "C"
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-7328466\",\n \"patient_mrn\": \"MRN-740510\",\n \"prescriber\": \"William Hebert\",\n \"date\": \"2026-01-04\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"BID\",\n \"quantity\": 60\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-7328466</rx_id>\n<patient_mrn>MRN-740510</patient_mrn>\n<prescriber>William Hebert</prescriber>\n<date>2026-01-04</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>20mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Metformin</name>\n<dosage>20mg</dosage>\n<frequency>BID</frequency>\n<quantity>60</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 190
}
|
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-7328466</rx_id>
<patient_mrn>MRN-740510</patient_mrn>
<prescriber>William Hebert</prescriber>
<date>2026-01-04</date>
<medications>
<name>Lisinopril</name>
<dosage>20mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medications>
<medications>
<name>Metformin</name>
<dosage>20mg</dosage>
<frequency>BID</frequency>
<quantity>60</quantity>
</medications>
</prescription>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"content\": \"Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\\nStrong who against entire.\\nKid television artist dream back agency. Need main ago investment job behavior.\",\n \"published\": \"2026-01-03T04:54:27.964292\",\n \"views\": 73181,\n \"headline\": \"Vision-oriented analyzing groupware\",\n \"section\": \"Business\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<content>Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\nStrong who against entire.\nKid television artist dream back agency. Need main ago investment job behavior.</content>\n<published>2026-01-03T04:54:27.964292</published>\n<views>73181</views>\n<headline>Vision-oriented analyzing groupware</headline>\n<section>Business</section>\n</news_article>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 193
}
|
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<content>Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.
Strong who against entire.
Kid television artist dream back agency. Need main ago investment job behavior.</content>
<published>2026-01-03T04:54:27.964292</published>
<views>73181</views>
<headline>Vision-oriented analyzing groupware</headline>
<section>Business</section>
</news_article>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the data below from YAML to TOML:\ndate: '2026-01-04'\nuser_id: d6e6e646-61a4-4af9-a9a1-d03d234244eb\ncontent: 'It herself scene five side support onto. Shake fear western believe. Say\n fact shoulder investment television pretty suffer.\n\n Ground listen official hand at indeed. Effort thus wife control.'\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from YAML to TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\ndate = \"2026-01-04\"\nuser_id = \"d6e6e646-61a4-4af9-a9a1-d03d234244eb\"\ncontent = \"It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\\nGround listen official hand at indeed. Effort thus wife control.\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 144
}
|
date = "2026-01-04"
user_id = "d6e6e646-61a4-4af9-a9a1-d03d234244eb"
content = "It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\nGround listen official hand at indeed. Effort thus wife control."
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-9719971\",\n \"patient_mrn\": \"MRN-909141\",\n \"prescriber\": \"Heather Stephens\",\n \"date\": \"2026-01-05\",\n \"medications\": [\n {\n \"name\": \"Atorvastatin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"daily\",\n \"quantity\": 30\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-9719971</rx_id>\n<patient_mrn>MRN-909141</patient_mrn>\n<prescriber>Heather Stephens</prescriber>\n<date>2026-01-05</date>\n<medications>\n<name>Atorvastatin</name>\n<dosage>20mg</dosage>\n<frequency>daily</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 160
}
|
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-9719971</rx_id>
<patient_mrn>MRN-909141</patient_mrn>
<prescriber>Heather Stephens</prescriber>
<date>2026-01-05</date>
<medications>
<name>Atorvastatin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>30</quantity>
</medications>
</prescription>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<value>911148</value>\n<contract_id>CTR-919818</contract_id>\n<parties>\n<name>Riggs, Carey and Rojas</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Mcdowell-Koch</name>\n<role>party_b</role>\n</parties>\n<status>active</status>\n<term_months>18</term_months>\n</contract>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"value\": 911148,\n \"contract_id\": \"CTR-919818\",\n \"parties\": [\n {\n \"name\": \"Riggs, Carey and Rojas\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Mcdowell-Koch\",\n \"role\": \"party_b\"\n }\n ],\n \"status\": \"active\",\n \"term_months\": 18\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 143
}
|
{
"value": 911148,
"contract_id": "CTR-919818",
"parties": [
{
"name": "Riggs, Carey and Rojas",
"role": "party_a"
},
{
"name": "Mcdowell-Koch",
"role": "party_b"
}
],
"status": "active",
"term_months": 18
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Organic analyzing strategy API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/similar\": {\n \"get\": {\n \"summary\": \"Natural see lot recently.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Organic analyzing strategy API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</similar>\n<get>\n<summary>Natural see lot recently.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<parameters>\n<name>param1</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//similar>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 224
}
|
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Organic analyzing strategy API</title>
<version>1.0.0</version>
</info>
<paths>
</similar>
<get>
<summary>Natural see lot recently.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//similar>
</paths>
</api_specification>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id: POST-86898750\nplatform: instagram\nuser_id: a47ec401-ca4e-44b5-afc7-6c2b372f589e\nusername: dylan00\ncontent: 'Might north politics.\n\n Moment bad without change physical store call. Enjoy question state student political\n boy tonight.\n\n Soon ten last small develop left enter. Health lead bank and air capital save.'\ntimestamp: '2026-01-07T13:51:25.591017'\nhashtags:\n- '#kid'\n- '#off'\n- '#school'\n- '#fund'\nengagement:\n likes: 9146\n shares: 205\n comments: 18\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 196
}
|
post_id: POST-86898750
platform: instagram
user_id: a47ec401-ca4e-44b5-afc7-6c2b372f589e
username: dylan00
content: 'Might north politics.
Moment bad without change physical store call. Enjoy question state student political
boy tonight.
Soon ten last small develop left enter. Health lead bank and air capital save.'
timestamp: '2026-01-07T13:51:25.591017'
hashtags:
- '#kid'
- '#off'
- '#school'
- '#fund'
engagement:
likes: 9146
shares: 205
comments: 18
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate error log data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: fd278ff8-fdfc-4b1d-81ec-31cf5ce70502\ntimestamp: '2026-01-07T13:51:26.554266'\nlevel: ERROR\nservice: heartService\nmessage: Attack candidate in give wish tree.\nstack_trace:\n- at thousand.py:354\n- at forget.py:20\n- at consider.py:392\ncontext:\n user_id: d753ac0c-8931-4c37-8bd5-01413aaaba41\n request_id: b35b2bd7-dc59-4d80-ba5d-dc21fa7f0bf7\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 163
}
|
error_id: fd278ff8-fdfc-4b1d-81ec-31cf5ce70502
timestamp: '2026-01-07T13:51:26.554266'
level: ERROR
service: heartService
message: Attack candidate in give wish tree.
stack_trace:
- at thousand.py:354
- at forget.py:20
- at consider.py:392
context:
user_id: d753ac0c-8931-4c37-8bd5-01413aaaba41
request_id: b35b2bd7-dc59-4d80-ba5d-dc21fa7f0bf7
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<assessment_id>ASMT-458464</assessment_id>\n<student_id>STU-453066</student_id>\n<course_id>CRS-7675</course_id>\n<type>assignment</type>\n<date>2026-01-06</date>\n<scores>\n<question>1</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>2</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>67</total_score>\n<percentage>65.79</percentage>\n<grade>B</grade>\n</student_assessment>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"assessment_id\": \"ASMT-458464\",\n \"student_id\": \"STU-453066\",\n \"course_id\": \"CRS-7675\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-06\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 8,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 67,\n \"percentage\": 65.79,\n \"grade\": \"B\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 332
}
|
{
"assessment_id": "ASMT-458464",
"student_id": "STU-453066",
"course_id": "CRS-7675",
"type": "assignment",
"date": "2026-01-06",
"scores": [
{
"question": 1,
"points_earned": 0,
"points_possible": 10
},
{
"question": 2,
"points_earned": 9,
"points_possible": 10
},
{
"question": 3,
"points_earned": 2,
"points_possible": 10
},
{
"question": 4,
"points_earned": 4,
"points_possible": 10
},
{
"question": 5,
"points_earned": 4,
"points_possible": 10
},
{
"question": 6,
"points_earned": 0,
"points_possible": 10
},
{
"question": 7,
"points_earned": 3,
"points_possible": 10
},
{
"question": 8,
"points_earned": 7,
"points_possible": 10
},
{
"question": 9,
"points_earned": 8,
"points_possible": 10
}
],
"total_score": 67,
"percentage": 65.79,
"grade": "B"
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntxn_id: TXN-59995807\ncustomer_id: 0d66cadd-c42f-4e9b-ae40-46d71f47623d\ntimestamp: '2026-01-07T13:51:27.084892'\nitems:\n- sku: SKU-83766\n qty: 4\n price: 55.35\n- sku: SKU-77209\n qty: 2\n price: 217.97\n- sku: SKU-11210\n qty: 5\n price: 436.04\nsubtotal: 1600.85\ntax: 34.84\ntotal: 602.79\npayment_method: apple_pay\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 157
}
|
txn_id: TXN-59995807
customer_id: 0d66cadd-c42f-4e9b-ae40-46d71f47623d
timestamp: '2026-01-07T13:51:27.084892'
items:
- sku: SKU-83766
qty: 4
price: 55.35
- sku: SKU-77209
qty: 2
price: 217.97
- sku: SKU-11210
qty: 5
price: 436.04
subtotal: 1600.85
tax: 34.84
total: 602.79
payment_method: apple_pay
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nitems:\n- sku: SKU-71565\n qty: 1\n price: 387.38\n- sku: SKU-23891\n qty: 1\n price: 432.74\n- sku: SKU-77840\n qty: 1\n price: 463.12\n- sku: SKU-27496\n qty: 3\n price: 295.3\ntax: 39.55\ntotal: 1865.58\ncustomer_id: bf96f80b-072c-4f04-82b0-c235c01681a8\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 142
}
|
items:
- sku: SKU-71565
qty: 1
price: 387.38
- sku: SKU-23891
qty: 1
price: 432.74
- sku: SKU-77840
qty: 1
price: 463.12
- sku: SKU-27496
qty: 3
price: 295.3
tax: 39.55
total: 1865.58
customer_id: bf96f80b-072c-4f04-82b0-c235c01681a8
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output lab result as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id: LAB-3793814\npatient_mrn: MRN-247204\norder_date: '2026-01-03'\npanel: CBC\nresults:\n- test: Hemoglobin\n value: 188.2\n unit: g/dL\n flag: low\n- test: WBC\n value: 197.7\n unit: mg/dL\n flag: high\n- test: Glucose\n value: 196.4\n unit: mg/dL\n flag: high\n- test: Glucose\n value: 193.9\n unit: g/dL\n flag: high\n- test: Glucose\n value: 197.2\n unit: g/dL\n flag: low\n- test: Hemoglobin\n value: 109.5\n unit: mg/dL\n flag: normal\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 186
}
|
result_id: LAB-3793814
patient_mrn: MRN-247204
order_date: '2026-01-03'
panel: CBC
results:
- test: Hemoglobin
value: 188.2
unit: g/dL
flag: low
- test: WBC
value: 197.7
unit: mg/dL
flag: high
- test: Glucose
value: 196.4
unit: mg/dL
flag: high
- test: Glucose
value: 193.9
unit: g/dL
flag: high
- test: Glucose
value: 197.2
unit: g/dL
flag: low
- test: Hemoglobin
value: 109.5
unit: mg/dL
flag: normal
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<sales_analytics>\n<period>September 2022</period>\n<total_revenue>4880286</total_revenue>\n<units_sold>74173</units_sold>\n<channels>\n<name>retail</name>\n<revenue>2000312</revenue>\n<growth>0.96</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>3751658</revenue>\n<growth>-3.19</growth>\n</channels>\n<top_products>\n<sku>SKU-6977</sku>\n<sales>264067</sales>\n</top_products>\n<top_products>\n<sku>SKU-7032</sku>\n<sales>443161</sales>\n</top_products>\n<top_products>\n<sku>SKU-1793</sku>\n<sales>209512</sales>\n</top_products>\n</sales_analytics>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from XML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nperiod: September 2022\ntotal_revenue: 4880286\nunits_sold: 74173\nchannels:\n- name: retail\n revenue: 2000312\n growth: 0.96\n- name: wholesale\n revenue: 3751658\n growth: -3.19\ntop_products:\n- sku: SKU-6977\n sales: 264067\n- sku: SKU-7032\n sales: 443161\n- sku: SKU-1793\n sales: 209512\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 150
}
|
period: September 2022
total_revenue: 4880286
units_sold: 74173
channels:
- name: retail
revenue: 2000312
growth: 0.96
- name: wholesale
revenue: 3751658
growth: -3.19
top_products:
- sku: SKU-6977
sales: 264067
- sku: SKU-7032
sales: 443161
- sku: SKU-1793
sales: 209512
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id = \"REV-7169946\"\nproduct_id = \"PROD-908355\"\nuser_id = \"109a43ce-0a9d-47ca-b5cc-5940dcb3a5c0\"\nrating = 3\ntitle = \"Suffer kid daughter race still baby.\"\ncontent = \"Young lot card leave book. Thank agency tree shake. Manage organization reduce from sort soldier.\\nRun rich marriage parent discover kitchen. Positive person baby list positive really range.\"\ndate = \"2026-01-05\"\nverified_purchase = true\nhelpful_votes = 3\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 180
}
|
review_id = "REV-7169946"
product_id = "PROD-908355"
user_id = "109a43ce-0a9d-47ca-b5cc-5940dcb3a5c0"
rating = 3
title = "Suffer kid daughter race still baby."
content = "Young lot card leave book. Thank agency tree shake. Manage organization reduce from sort soldier.\nRun rich marriage parent discover kitchen. Positive person baby list positive really range."
date = "2026-01-05"
verified_purchase = true
helpful_votes = 3
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"rx_id\": \"RX-9458448\",\n \"patient_mrn\": \"MRN-362998\",\n \"prescriber\": \"Courtney Hansen\",\n \"date\": \"2026-01-02\",\n \"medications\": [\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"10mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert prescription from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prescription>\n<rx_id>RX-9458448</rx_id>\n<patient_mrn>MRN-362998</patient_mrn>\n<prescriber>Courtney Hansen</prescriber>\n<date>2026-01-02</date>\n<medications>\n<name>Lisinopril</name>\n<dosage>10mg</dosage>\n<frequency>BID</frequency>\n<quantity>30</quantity>\n</medications>\n</prescription>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "conversion",
"estimated_tokens": 159
}
|
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-9458448</rx_id>
<patient_mrn>MRN-362998</patient_mrn>
<prescriber>Courtney Hansen</prescriber>
<date>2026-01-02</date>
<medications>
<name>Lisinopril</name>
<dosage>10mg</dosage>
<frequency>BID</frequency>
<quantity>30</quantity>
</medications>
</prescription>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-685161</product_id>\n<name>Balanced demand-driven capacity</name>\n<category>clothing</category>\n<price>554.83</price>\n<currency>USD</currency>\n<stock>872</stock>\n<is_available>True</is_available>\n<rating>3.32</rating>\n<reviews>212</reviews>\n<specs>\n<weight_kg>39.83</weight_kg>\n<dimensions>86x88x63cm</dimensions>\n</specs>\n</product_listing>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"product_id\": \"PROD-685161\",\n \"name\": \"Balanced demand-driven capacity\",\n \"category\": \"clothing\",\n \"price\": 554.83,\n \"currency\": \"USD\",\n \"stock\": 872,\n \"is_available\": true,\n \"rating\": 3.32,\n \"reviews\": 212,\n \"specs\": {\n \"weight_kg\": 39.83,\n \"dimensions\": \"86x88x63cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 152
}
|
{
"product_id": "PROD-685161",
"name": "Balanced demand-driven capacity",
"category": "clothing",
"price": 554.83,
"currency": "USD",
"stock": 872,
"is_available": true,
"rating": 3.32,
"reviews": 212,
"specs": {
"weight_kg": 39.83,
"dimensions": "86x88x63cm"
}
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate prescription data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"rx_id\": \"RX-9442688\",\n \"patient_mrn\": \"MRN-277514\",\n \"prescriber\": \"Timothy Goodman\",\n \"date\": \"2026-01-04\",\n \"medications\": [\n {\n \"name\": \"Metformin\",\n \"dosage\": \"20mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Metformin\",\n \"dosage\": \"5mg\",\n \"frequency\": \"BID\",\n \"quantity\": 30\n },\n {\n \"name\": \"Lisinopril\",\n \"dosage\": \"5mg\",\n \"frequency\": \"TID\",\n \"quantity\": 30\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 195
}
|
{
"rx_id": "RX-9442688",
"patient_mrn": "MRN-277514",
"prescriber": "Timothy Goodman",
"date": "2026-01-04",
"medications": [
{
"name": "Metformin",
"dosage": "20mg",
"frequency": "TID",
"quantity": 30
},
{
"name": "Metformin",
"dosage": "5mg",
"frequency": "BID",
"quantity": 30
},
{
"name": "Lisinopril",
"dosage": "5mg",
"frequency": "TID",
"quantity": 30
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Business-focused zero administration encryption API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/teach\": {\n \"get\": {\n \"summary\": \"Government trade direction personal reason hundred\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 252
}
|
{
"openapi": "3.0.0",
"info": {
"title": "Business-focused zero administration encryption API",
"version": "1.0.0"
},
"paths": {
"/teach": {
"get": {
"summary": "Government trade direction personal reason hundred",
"parameters": [
{
"name": "param0",
"in": "query",
"type": "string"
},
{
"name": "param1",
"in": "query",
"type": "string"
}
],
"responses": {
"200": {
"description": "Success"
},
"400": {
"description": "Bad Request"
}
}
}
}
}
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<title>Exactly almost full new record save.</title>\n<date>2026-01-02</date>\n<product_id>PROD-922306</product_id>\n<content>Arrive much low will teach. By possible nature learn could. Act hot whole guy experience.\nIdentify world fight stock. Force fear soon. Author night think.</content>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"title\": \"Exactly almost full new record save.\",\n \"date\": \"2026-01-02\",\n \"product_id\": \"PROD-922306\",\n \"content\": \"Arrive much low will teach. By possible nature learn could. Act hot whole guy experience.\\nIdentify world fight stock. Force fear soon. Author night think.\"\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 150
}
|
{
"title": "Exactly almost full new record save.",
"date": "2026-01-02",
"product_id": "PROD-922306",
"content": "Arrive much low will teach. By possible nature learn could. Act hot whole guy experience.\nIdentify world fight stock. Force fear soon. Author night think."
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output social media post as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-46905875\"\nplatform = \"instagram\"\nuser_id = \"2079b341-d50b-4860-ba15-aa28bbe0f5b3\"\nusername = \"xhernandez\"\ncontent = \"Serious degree upon late.\\nPainting throughout direction indicate night. Political business voice street child. Across between ready. Majority red mission prepare state.\"\ntimestamp = \"2026-01-07T13:51:26.735117\"\nhashtags = [ \"#easy\", \"#miss\",]\n\n[engagement]\nlikes = 6808\nshares = 9\ncomments = 24\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 182
}
|
post_id = "POST-46905875"
platform = "instagram"
user_id = "2079b341-d50b-4860-ba15-aa28bbe0f5b3"
username = "xhernandez"
content = "Serious degree upon late.\nPainting throughout direction indicate night. Political business voice street child. Across between ready. Majority red mission prepare state."
timestamp = "2026-01-07T13:51:26.735117"
hashtags = [ "#easy", "#miss",]
[engagement]
likes = 6808
shares = 9
comments = 24
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"instructor\": \"Tamara Stark\",\n \"term\": \"Spring 2022\",\n \"code\": \"VMA483\",\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<instructor>Tamara Stark</instructor>\n<term>Spring 2022</term>\n<code>VMA483</code>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 140
}
|
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<instructor>Tamara Stark</instructor>
<term>Spring 2022</term>
<code>VMA483</code>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Create a YAML representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Snow, Shelton and Parsons\nticker: LYEH\nquarter: Q3 2022\nrevenue: 49988929\nexpenses: 3428077\nnet_income: 8543670\neps: 3.41\nmetrics:\n profit_margin: 11.21\n roe: 5.99\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 121
}
|
company: Snow, Shelton and Parsons
ticker: LYEH
quarter: Q3 2022
revenue: 49988929
expenses: 3428077
net_income: 8543670
eps: 3.41
metrics:
profit_margin: 11.21
roe: 5.99
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate social media post data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-18209344\"\nplatform = \"facebook\"\nuser_id = \"8880ae5d-22ce-466e-ac5d-224201417b5e\"\nusername = \"xmcbride\"\ncontent = \"Determine live compare center as direction. Eye experience low wear. If south level.\\nWorry expect style camera. Scene majority pay voice television professor.\"\ntimestamp = \"2026-01-07T13:51:27.602464\"\nhashtags = [ \"#culture\", \"#whole\", \"#central\",]\n\n[engagement]\nlikes = 2214\nshares = 878\ncomments = 146\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 184
}
|
post_id = "POST-18209344"
platform = "facebook"
user_id = "8880ae5d-22ce-466e-ac5d-224201417b5e"
username = "xmcbride"
content = "Determine live compare center as direction. Eye experience low wear. If south level.\nWorry expect style camera. Scene majority pay voice television professor."
timestamp = "2026-01-07T13:51:27.602464"
hashtags = [ "#culture", "#whole", "#central",]
[engagement]
likes = 2214
shares = 878
comments = 146
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output prescription as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-9001624\npatient_mrn: MRN-695608\nprescriber: Stephen Davis\ndate: '2026-01-05'\nmedications:\n- name: Lisinopril\n dosage: 20mg\n frequency: daily\n quantity: 90\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
rx_id: RX-9001624
patient_mrn: MRN-695608
prescriber: Stephen Davis
date: '2026-01-05'
medications:
- name: Lisinopril
dosage: 20mg
frequency: daily
quantity: 90
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate clinical note data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"note_id\": \"CN-6952117\",\n \"patient\": {\n \"mrn\": \"MRN-227055\",\n \"age\": 50,\n \"gender\": \"F\"\n },\n \"encounter_date\": \"2026-01-03\",\n \"chief_complaint\": \"headache\",\n \"vitals\": {\n \"bp\": \"146/78\",\n \"hr\": 63,\n \"temp_f\": 97.9\n },\n \"assessment\": [\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"J35\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"K44\"\n },\n {\n \"problem\": \"hypertension\",\n \"icd10\": \"I58\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 194
}
|
{
"note_id": "CN-6952117",
"patient": {
"mrn": "MRN-227055",
"age": 50,
"gender": "F"
},
"encounter_date": "2026-01-03",
"chief_complaint": "headache",
"vitals": {
"bp": "146/78",
"hr": 63,
"temp_f": 97.9
},
"assessment": [
{
"problem": "hypertension",
"icd10": "J35"
},
{
"problem": "hypertension",
"icd10": "K44"
},
{
"problem": "hypertension",
"icd10": "I58"
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate transaction record data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"txn_id\": \"TXN-13058367\",\n \"customer_id\": \"852e4544-1bd4-44f1-abf0-2ff01b4a4792\",\n \"timestamp\": \"2026-01-07T13:51:26.835091\",\n \"items\": [\n {\n \"sku\": \"SKU-47822\",\n \"qty\": 3,\n \"price\": 237.72\n },\n {\n \"sku\": \"SKU-38430\",\n \"qty\": 4,\n \"price\": 285.9\n },\n {\n \"sku\": \"SKU-22327\",\n \"qty\": 1,\n \"price\": 141.71\n }\n ],\n \"subtotal\": 408.33,\n \"tax\": 11.32,\n \"total\": 1142.29,\n \"payment_method\": \"paypal\"\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 195
}
|
{
"txn_id": "TXN-13058367",
"customer_id": "852e4544-1bd4-44f1-abf0-2ff01b4a4792",
"timestamp": "2026-01-07T13:51:26.835091",
"items": [
{
"sku": "SKU-47822",
"qty": 3,
"price": 237.72
},
{
"sku": "SKU-38430",
"qty": 4,
"price": 285.9
},
{
"sku": "SKU-22327",
"qty": 1,
"price": 141.71
}
],
"subtotal": 408.33,
"tax": 11.32,
"total": 1142.29,
"payment_method": "paypal"
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Convert the following TOML to YAML:\nerror_id = \"92d36993-19b1-4c19-9b64-8b4669c6636f\"\ntimestamp = \"2026-01-07T13:51:27.222487\"\nlevel = \"WARNING\"\nservice = \"voiceService\"\nmessage = \"Analysis beautiful attack blue eye.\"\nstack_trace = [ \"at well.py:163\", \"at will.py:421\", \"at run.py:384\", \"at TV.py:103\",]\n\n[context]\nuser_id = \"c92bcb8f-c109-47f8-aa13-b43737a1fc38\"\nrequest_id = \"f4cb6737-30c9-41ef-814b-34c3ec971deb\"\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from TOML to YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nerror_id: 92d36993-19b1-4c19-9b64-8b4669c6636f\ntimestamp: '2026-01-07T13:51:27.222487'\nlevel: WARNING\nservice: voiceService\nmessage: Analysis beautiful attack blue eye.\nstack_trace:\n- at well.py:163\n- at will.py:421\n- at run.py:384\n- at TV.py:103\ncontext:\n user_id: c92bcb8f-c109-47f8-aa13-b43737a1fc38\n request_id: f4cb6737-30c9-41ef-814b-34c3ec971deb\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 166
}
|
error_id: 92d36993-19b1-4c19-9b64-8b4669c6636f
timestamp: '2026-01-07T13:51:27.222487'
level: WARNING
service: voiceService
message: Analysis beautiful attack blue eye.
stack_trace:
- at well.py:163
- at will.py:421
- at run.py:384
- at TV.py:103
context:
user_id: c92bcb8f-c109-47f8-aa13-b43737a1fc38
request_id: f4cb6737-30c9-41ef-814b-34c3ec971deb
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Reformat the data below from CSV to TOML:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\n\"Relate make read game soldier new. Agree south attorney one century drive draw.\nReduce head tax cert\",\"[{\"\"name\"\": \"\"Ashley Hubbard\"\", \"\"affiliation\"\": \"\"Mcdonald-White\"\", \"\"email\"\": \"\"jenniferlong@example.net\"\"}, {\",65,Parsons Inc,\"[\"\"gas\"\", \"\"understand\"\", \"\"everything\"\", \"\"miss\"\"]\",arXiv:2024.49729,10.3465/hMKF,Cell,2024,Optimized fault-tolerant monitoring\r\nQuite personal enough like wrong. Type use social step lead action attack. Second high impact paper.,\"[{\"\"name\"\": \"\"Shawn Fischer\"\", \"\"affiliation\"\": \"\"Leblanc-Long\"\", \"\"email\"\": \"\"holmesmichelle@example.org\"\"}, {\"\"\",480,None,\"[\"\"speech\"\", \"\"language\"\", \"\"wife\"\", \"\"old\"\"]\",arXiv:2022.59733,10.1750/XgMv,Nature,2020,Re-engineered clear-thinking Internet solution\r\nAffect change either money commercial. Often allow wish suffer person.,\"[{\"\"name\"\": \"\"Shannon Huber\"\", \"\"affiliation\"\": \"\"Erickson-Flynn\"\", \"\"email\"\": \"\"singhjeffrey@example.org\"\"}, {\"\"\",229,None,\"[\"\"edge\"\", \"\"friend\"\", \"\"develop\"\", \"\"reflect\"\"]\",arXiv:2023.25133,10.6743/gNVb,Nature,2023,Innovative full-range projection\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper from CSV to TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\npaper_id = \"arXiv:2024.49729\"\ntitle = \"Optimized fault-tolerant monitoring\"\nabstract = \"Relate make read game soldier new. Agree south attorney one century drive draw.\\nReduce head tax certainly offer deal. Sister station adult seat wear.\"\nkeywords = [ \"gas\", \"understand\", \"everything\", \"miss\",]\ncitations = 65\nfunding_source = \"Parsons Inc\"\n[[authors]]\nname = \"Ashley Hubbard\"\naffiliation = \"Mcdonald-White\"\nemail = \"jenniferlong@example.net\"\n\n[[authors]]\nname = \"Erica Marshall\"\naffiliation = \"Calderon-Dalton\"\nemail = \"adouglas@example.org\"\n\n[[authors]]\nname = \"Mercedes Campbell\"\naffiliation = \"Davis-Lynch\"\nemail = \"yharris@example.org\"\n\n[publication]\nvenue = \"Cell\"\nyear = 2024\ndoi = \"10.3465/hMKF\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 251
}
|
paper_id = "arXiv:2024.49729"
title = "Optimized fault-tolerant monitoring"
abstract = "Relate make read game soldier new. Agree south attorney one century drive draw.\nReduce head tax certainly offer deal. Sister station adult seat wear."
keywords = [ "gas", "understand", "everything", "miss",]
citations = 65
funding_source = "Parsons Inc"
[[authors]]
name = "Ashley Hubbard"
affiliation = "Mcdonald-White"
email = "jenniferlong@example.net"
[[authors]]
name = "Erica Marshall"
affiliation = "Calderon-Dalton"
email = "adouglas@example.org"
[[authors]]
name = "Mercedes Campbell"
affiliation = "Davis-Lynch"
email = "yharris@example.org"
[publication]
venue = "Cell"
year = 2024
doi = "10.3465/hMKF"
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"June 2021\",\n \"total_revenue\": 1467254,\n \"units_sold\": 63744,\n \"channels\": [\n {\n \"name\": \"wholesale\",\n \"revenue\": 2975287,\n \"growth\": -1.88\n },\n {\n \"name\": \"online\",\n \"revenue\": 2665464,\n \"growth\": 14.77\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-1172\",\n \"sales\": 348860\n },\n {\n \"sku\": \"SKU-4431\",\n \"sales\": 479568\n },\n {\n \"sku\": \"SKU-6244\",\n \"sales\": 245719\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
{
"period": "June 2021",
"total_revenue": 1467254,
"units_sold": 63744,
"channels": [
{
"name": "wholesale",
"revenue": 2975287,
"growth": -1.88
},
{
"name": "online",
"revenue": 2665464,
"growth": 14.77
}
],
"top_products": [
{
"sku": "SKU-1172",
"sales": 348860
},
{
"sku": "SKU-4431",
"sales": 479568
},
{
"sku": "SKU-6244",
"sales": 245719
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate financial report data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncompany: Smith-Glover\nticker: JROI\nquarter: Q3 2023\nrevenue: 95238846\nexpenses: 30652579\nnet_income: 5856951\neps: 7.31\nmetrics:\n profit_margin: 9.94\n roe: 10.91\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 118
}
|
company: Smith-Glover
ticker: JROI
quarter: Q3 2023
revenue: 95238846
expenses: 30652579
net_income: 5856951
eps: 7.31
metrics:
profit_margin: 9.94
roe: 10.91
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<assessment_id>ASMT-577861</assessment_id>\n<student_id>STU-664280</student_id>\n<course_id>CRS-8099</course_id>\n<type>exam</type>\n<date>2026-01-06</date>\n<scores>\n<question>1</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>3</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>52</total_score>\n<percentage>81.98</percentage>\n<grade>B</grade>\n</student_assessment>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert student assessment from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"assessment_id\": \"ASMT-577861\",\n \"student_id\": \"STU-664280\",\n \"course_id\": \"CRS-8099\",\n \"type\": \"exam\",\n \"date\": \"2026-01-06\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 3,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 1,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 52,\n \"percentage\": 81.98,\n \"grade\": \"B\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 287
}
|
{
"assessment_id": "ASMT-577861",
"student_id": "STU-664280",
"course_id": "CRS-8099",
"type": "exam",
"date": "2026-01-06",
"scores": [
{
"question": 1,
"points_earned": 7,
"points_possible": 10
},
{
"question": 2,
"points_earned": 0,
"points_possible": 10
},
{
"question": 3,
"points_earned": 5,
"points_possible": 10
},
{
"question": 4,
"points_earned": 6,
"points_possible": 10
},
{
"question": 5,
"points_earned": 3,
"points_possible": 10
},
{
"question": 6,
"points_earned": 0,
"points_possible": 10
},
{
"question": 7,
"points_earned": 1,
"points_possible": 10
}
],
"total_score": 52,
"percentage": 81.98,
"grade": "B"
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course_id>CRS-1797</course_id>\n<code>QAA477</code>\n<title>User-friendly composite interface 101</title>\n<instructor>Selena Walker</instructor>\n<credits>4</credits>\n<term>Fall 2024</term>\n<schedule>\n<week>1</week>\n<topic>all</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>education</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>will</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>operation</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>western</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>plan</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>allow</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"course_id\": \"CRS-1797\",\n \"code\": \"QAA477\",\n \"title\": \"User-friendly composite interface 101\",\n \"instructor\": \"Selena Walker\",\n \"credits\": 4,\n \"term\": \"Fall 2024\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"all\"\n },\n {\n \"week\": 2,\n \"topic\": \"education\"\n },\n {\n \"week\": 3,\n \"topic\": \"will\"\n },\n {\n \"week\": 4,\n \"topic\": \"operation\"\n },\n {\n \"week\": 5,\n \"topic\": \"western\"\n },\n {\n \"week\": 6,\n \"topic\": \"plan\"\n },\n {\n \"week\": 7,\n \"topic\": \"allow\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 240
}
|
{
"course_id": "CRS-1797",
"code": "QAA477",
"title": "User-friendly composite interface 101",
"instructor": "Selena Walker",
"credits": 4,
"term": "Fall 2024",
"schedule": [
{
"week": 1,
"topic": "all"
},
{
"week": 2,
"topic": "education"
},
{
"week": 3,
"topic": "will"
},
{
"week": 4,
"topic": "operation"
},
{
"week": 5,
"topic": "western"
},
{
"week": 6,
"topic": "plan"
},
{
"week": 7,
"topic": "allow"
}
],
"grading": {
"homework": 30,
"midterm": 30,
"final": 40
}
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<clinical_note>\n<note_id>CN-6224145</note_id>\n<patient>\n<mrn>MRN-560569</mrn>\n<age>88</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-04</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>119/73</bp>\n<hr>63</hr>\n<temp_f>100.0</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>I32</icd10>\n</assessment>\n</clinical_note>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 180
}
|
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-6224145</note_id>
<patient>
<mrn>MRN-560569</mrn>
<age>88</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-04</encounter_date>
<chief_complaint>headache</chief_complaint>
<vitals>
<bp>119/73</bp>
<hr>63</hr>
<temp_f>100.0</temp_f>
</vitals>
<assessment>
<problem>hypertension</problem>
<icd10>I32</icd10>
</assessment>
</clinical_note>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output customer review as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nreview_id = \"REV-1369973\"\nproduct_id = \"PROD-861575\"\nuser_id = \"a55bb48c-5dcb-464a-b952-9d377a4cb9c4\"\nrating = 1\ntitle = \"Relationship job find one allow law through.\"\ncontent = \"Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land.\"\ndate = \"2026-01-02\"\nverified_purchase = true\nhelpful_votes = 8\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 172
}
|
review_id = "REV-1369973"
product_id = "PROD-861575"
user_id = "a55bb48c-5dcb-464a-b952-9d377a4cb9c4"
rating = 1
title = "Relationship job find one allow law through."
content = "Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land."
date = "2026-01-02"
verified_purchase = true
helpful_votes = 8
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"rating\": 4.54,\n \"stock\": 843,\n \"specs\": {\n \"weight_kg\": 34.7,\n \"dimensions\": \"61x86x65cm\"\n },\n \"currency\": \"USD\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<rating>4.54</rating>\n<stock>843</stock>\n<specs>\n<weight_kg>34.7</weight_kg>\n<dimensions>61x86x65cm</dimensions>\n</specs>\n<currency>USD</currency>\n</product_listing>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 135
}
|
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<rating>4.54</rating>
<stock>843</stock>
<specs>
<weight_kg>34.7</weight_kg>
<dimensions>61x86x65cm</dimensions>
</specs>
<currency>USD</currency>
</product_listing>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"contract_id\": \"CTR-313579\",\n \"parties\": [\n {\n \"name\": \"Roberts, Newton and Ortiz\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Garcia PLC\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 55,\n \"value\": 108642,\n \"status\": \"active\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-313579</contract_id>\n<parties>\n<name>Roberts, Newton and Ortiz</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Garcia PLC</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-01</effective_date>\n<term_months>55</term_months>\n<value>108642</value>\n<status>active</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 168
}
|
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-313579</contract_id>
<parties>
<name>Roberts, Newton and Ortiz</name>
<role>party_a</role>
</parties>
<parties>
<name>Garcia PLC</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-01</effective_date>
<term_months>55</term_months>
<value>108642</value>
<status>active</status>
</contract>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate prescription data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-9036427\npatient_mrn: MRN-461250\nprescriber: Zachary Berry\ndate: '2026-01-01'\nmedications:\n- name: Atorvastatin\n dosage: 5mg\n frequency: daily\n quantity: 30\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
rx_id: RX-9036427
patient_mrn: MRN-461250
prescriber: Zachary Berry
date: '2026-01-01'
medications:
- name: Atorvastatin
dosage: 5mg
frequency: daily
quantity: 30
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate prescription data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-5523111\"\ndate = \"2026-01-01\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"10mg\"\nfrequency = \"BID\"\nquantity = 60\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 106
}
|
rx_id = "RX-5523111"
date = "2026-01-01"
[[medications]]
name = "Atorvastatin"
dosage = "10mg"
frequency = "BID"
quantity = 60
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<article_id>ART-5347545</article_id>\n<headline>Triple-buffered zero administration algorithm</headline>\n<author>Martha Brown</author>\n<published>2026-01-05T16:28:34.342789</published>\n<section>Sports</section>\n<content>Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point white.\nTake many this never ever trip. Specific call according. We argue person federal central each.</content>\n<tags>line</tags>\n<tags>true</tags>\n<tags>compare</tags>\n<tags>for</tags>\n<views>96946</views>\n<shares>1479</shares>\n</news_article>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"article_id\": \"ART-5347545\",\n \"headline\": \"Triple-buffered zero administration algorithm\",\n \"author\": \"Martha Brown\",\n \"published\": \"2026-01-05T16:28:34.342789\",\n \"section\": \"Sports\",\n \"content\": \"Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point white.\\nTake many this never ever trip. Specific call according. We argue person federal central each.\",\n \"tags\": [\n \"line\",\n \"true\",\n \"compare\",\n \"for\"\n ],\n \"views\": 96946,\n \"shares\": 1479\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 210
}
|
{
"article_id": "ART-5347545",
"headline": "Triple-buffered zero administration algorithm",
"author": "Martha Brown",
"published": "2026-01-05T16:28:34.342789",
"section": "Sports",
"content": "Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point white.\nTake many this never ever trip. Specific call according. We argue person federal central each.",
"tags": [
"line",
"true",
"compare",
"for"
],
"views": 96946,
"shares": 1479
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ntotal_score = 97\npercentage = 78.32\ncourse_id = \"CRS-4089\"\n[[scores]]\nquestion = 1\npoints_earned = 0\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 1\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 3\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 11\npoints_earned = 5\npoints_possible = 10\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 267
}
|
total_score = 97
percentage = 78.32
course_id = "CRS-4089"
[[scores]]
question = 1
points_earned = 0
points_possible = 10
[[scores]]
question = 2
points_earned = 4
points_possible = 10
[[scores]]
question = 3
points_earned = 10
points_possible = 10
[[scores]]
question = 4
points_earned = 5
points_possible = 10
[[scores]]
question = 5
points_earned = 4
points_possible = 10
[[scores]]
question = 6
points_earned = 2
points_possible = 10
[[scores]]
question = 7
points_earned = 1
points_possible = 10
[[scores]]
question = 8
points_earned = 5
points_possible = 10
[[scores]]
question = 9
points_earned = 3
points_possible = 10
[[scores]]
question = 10
points_earned = 9
points_possible = 10
[[scores]]
question = 11
points_earned = 5
points_possible = 10
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nerror_id: 6b141850-4372-44c1-8cf7-fc47780a5017\ntimestamp: '2026-01-07T13:51:26.727039'\nlevel: WARNING\nservice: fullService\nmessage: Simply human maintain sport.\nstack_trace:\n- at environmental.py:351\n- at develop.py:28\n- at send.py:431\ncontext:\n user_id: fad7b695-3fb8-4313-ad8d-c2b1d4034196\n request_id: 2ca5c81e-d6c8-42a4-9e09-9715e928fe91\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 162
}
|
error_id: 6b141850-4372-44c1-8cf7-fc47780a5017
timestamp: '2026-01-07T13:51:26.727039'
level: WARNING
service: fullService
message: Simply human maintain sport.
stack_trace:
- at environmental.py:351
- at develop.py:28
- at send.py:431
context:
user_id: fad7b695-3fb8-4313-ad8d-c2b1d4034196
request_id: 2ca5c81e-d6c8-42a4-9e09-9715e928fe91
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Horizontal interactive project API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/base\": {\n \"get\": {\n \"summary\": \"Management send father actually special image.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification from JSON to XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Horizontal interactive project API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</base>\n<get>\n<summary>Management send father actually special image.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>\n<description>Success</description>\n</200>\n<400>\n<description>Bad Request</description>\n</400>\n</responses>\n</get>\n<//base>\n</paths>\n</api_specification>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 208
}
|
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Horizontal interactive project API</title>
<version>1.0.0</version>
</info>
<paths>
</base>
<get>
<summary>Management send father actually special image.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//base>
</paths>
</api_specification>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"error_id\": \"91d16731-5e7b-4a47-8285-7a54d79d3b76\",\n \"timestamp\": \"2026-01-07T13:51:25.635487\",\n \"level\": \"WARNING\",\n \"service\": \"AmericanService\",\n \"message\": \"Drug sell certainly major total.\",\n \"stack_trace\": [\n \"at although.py:151\",\n \"at mission.py:443\"\n ],\n \"context\": {\n \"user_id\": \"11d85442-7276-4e30-9249-06df8089bd39\",\n \"request_id\": \"f3cc0b9c-f4db-4c9d-bea8-f49774b1a7e6\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 179
}
|
{
"error_id": "91d16731-5e7b-4a47-8285-7a54d79d3b76",
"timestamp": "2026-01-07T13:51:25.635487",
"level": "WARNING",
"service": "AmericanService",
"message": "Drug sell certainly major total.",
"stack_trace": [
"at although.py:151",
"at mission.py:443"
],
"context": {
"user_id": "11d85442-7276-4e30-9249-06df8089bd39",
"request_id": "f3cc0b9c-f4db-4c9d-bea8-f49774b1a7e6"
}
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate sales analytics data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"May 2020\",\n \"total_revenue\": 9864225,\n \"units_sold\": 74086,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 906832,\n \"growth\": -8.93\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 2437365,\n \"growth\": 2.73\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-7032\",\n \"sales\": 420063\n },\n {\n \"sku\": \"SKU-9360\",\n \"sales\": 149398\n },\n {\n \"sku\": \"SKU-9440\",\n \"sales\": 105905\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
{
"period": "May 2020",
"total_revenue": 9864225,
"units_sold": 74086,
"channels": [
{
"name": "online",
"revenue": 906832,
"growth": -8.93
},
{
"name": "wholesale",
"revenue": 2437365,
"growth": 2.73
}
],
"top_products": [
{
"sku": "SKU-7032",
"sales": 420063
},
{
"sku": "SKU-9360",
"sales": 149398
},
{
"sku": "SKU-9440",
"sales": 105905
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"post_id\": \"POST-86945311\",\n \"platform\": \"facebook\",\n \"user_id\": \"b9da037c-f6cd-4ced-8c95-ca7562cf6118\",\n \"username\": \"martinsteven\",\n \"content\": \"Forget late prevent year cold able arrive. Few possible himself sing community. Activity campaign sure south. Chance on none line best magazine education.\",\n \"timestamp\": \"2026-01-07T13:51:26.810240\",\n \"hashtags\": [\n \"#drop\",\n \"#consider\",\n \"#nature\",\n \"#all\"\n ],\n \"engagement\": {\n \"likes\": 3344,\n \"shares\": 900,\n \"comments\": 482\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<social_media_post>\n<post_id>POST-86945311</post_id>\n<platform>facebook</platform>\n<user_id>b9da037c-f6cd-4ced-8c95-ca7562cf6118</user_id>\n<username>martinsteven</username>\n<content>Forget late prevent year cold able arrive. Few possible himself sing community. Activity campaign sure south. Chance on none line best magazine education.</content>\n<timestamp>2026-01-07T13:51:26.810240</timestamp>\n<hashtags>#drop</hashtags>\n<hashtags>#consider</hashtags>\n<hashtags>#nature</hashtags>\n<hashtags>#all</hashtags>\n<engagement>\n<likes>3344</likes>\n<shares>900</shares>\n<comments>482</comments>\n</engagement>\n</social_media_post>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 244
}
|
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-86945311</post_id>
<platform>facebook</platform>
<user_id>b9da037c-f6cd-4ced-8c95-ca7562cf6118</user_id>
<username>martinsteven</username>
<content>Forget late prevent year cold able arrive. Few possible himself sing community. Activity campaign sure south. Chance on none line best magazine education.</content>
<timestamp>2026-01-07T13:51:26.810240</timestamp>
<hashtags>#drop</hashtags>
<hashtags>#consider</hashtags>
<hashtags>#nature</hashtags>
<hashtags>#all</hashtags>
<engagement>
<likes>3344</likes>
<shares>900</shares>
<comments>482</comments>
</engagement>
</social_media_post>
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following XML to JSON:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-7122533</review_id>\n<content>Expert difficult hot radio mission. Throw southern he book way media particular.</content>\n<rating>1</rating>\n<date>2026-01-06</date>\n<verified_purchase>False</verified_purchase>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from XML to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-7122533\",\n \"content\": \"Expert difficult hot radio mission. Throw southern he book way media particular.\",\n \"rating\": 1,\n \"date\": \"2026-01-06\",\n \"verified_purchase\": false\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 129
}
|
{
"review_id": "REV-7122533",
"content": "Expert difficult hot radio mission. Throw southern he book way media particular.",
"rating": 1,
"date": "2026-01-06",
"verified_purchase": false
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"order_date\": \"2026-01-05\",\n \"results\": [\n {\n \"test\": \"Hemoglobin\",\n \"value\": 95.5,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 52.7,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 142.9,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 146.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n }\n ],\n \"panel\": \"Lipid\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<order_date>2026-01-05</order_date>\n<results>\n<test>Hemoglobin</test>\n<value>95.5</value>\n<unit>g/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>52.7</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>142.9</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Glucose</test>\n<value>146.5</value>\n<unit>mg/dL</unit>\n<flag>high</flag>\n</results>\n<panel>Lipid</panel>\n</lab_result>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "lab_result",
"type": "conversion",
"estimated_tokens": 209
}
|
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<order_date>2026-01-05</order_date>
<results>
<test>Hemoglobin</test>
<value>95.5</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>52.7</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>142.9</value>
<unit>mg/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Glucose</test>
<value>146.5</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<panel>Lipid</panel>
</lab_result>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output error log as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>2d978d26-6fd7-4641-b202-43ebc0760711</error_id>\n<timestamp>2026-01-07T13:51:26.663970</timestamp>\n<level>WARNING</level>\n<service>someoneService</service>\n<message>Inside live none value unit Republican black.</message>\n<stack_trace>at role.py:276</stack_trace>\n<stack_trace>at loss.py:371</stack_trace>\n<context>\n<user_id>26f1b94c-c76e-47ab-9121-a3f8ec11053f</user_id>\n<request_id>ce096dca-f53f-40bf-822d-ed29d8ca8dd9</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 205
}
|
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>2d978d26-6fd7-4641-b202-43ebc0760711</error_id>
<timestamp>2026-01-07T13:51:26.663970</timestamp>
<level>WARNING</level>
<service>someoneService</service>
<message>Inside live none value unit Republican black.</message>
<stack_trace>at role.py:276</stack_trace>
<stack_trace>at loss.py:371</stack_trace>
<context>
<user_id>26f1b94c-c76e-47ab-9121-a3f8ec11053f</user_id>
<request_id>ce096dca-f53f-40bf-822d-ed29d8ca8dd9</request_id>
</context>
</error_log>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a customer review."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create customer review in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate = \"2026-01-04\"\nuser_id = \"d6e6e646-61a4-4af9-a9a1-d03d234244eb\"\ncontent = \"It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\\nGround listen official hand at indeed. Effort thus wife control.\"\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 143
}
|
date = "2026-01-04"
user_id = "d6e6e646-61a4-4af9-a9a1-d03d234244eb"
content = "It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\nGround listen official hand at indeed. Effort thus wife control."
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of sales analytics."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"period\": \"March 2022\",\n \"total_revenue\": 6503980,\n \"units_sold\": 7670,\n \"channels\": [\n {\n \"name\": \"retail\",\n \"revenue\": 3279241,\n \"growth\": 22.76\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 1469640,\n \"growth\": 16.07\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-8081\",\n \"sales\": 71747\n },\n {\n \"sku\": \"SKU-8211\",\n \"sales\": 475825\n },\n {\n \"sku\": \"SKU-4565\",\n \"sales\": 485553\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 196
}
|
{
"period": "March 2022",
"total_revenue": 6503980,
"units_sold": 7670,
"channels": [
{
"name": "retail",
"revenue": 3279241,
"growth": 22.76
},
{
"name": "wholesale",
"revenue": 1469640,
"growth": 16.07
}
],
"top_products": [
{
"sku": "SKU-8081",
"sales": 71747
},
{
"sku": "SKU-8211",
"sales": 475825
},
{
"sku": "SKU-4565",
"sales": 485553
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate prescription data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate = \"2026-01-06\"\npatient_mrn = \"MRN-259808\"\nrx_id = \"RX-8539167\"\nprescriber = \"Joseph Griffin\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"10mg\"\nfrequency = \"daily\"\nquantity = 90\n\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"10mg\"\nfrequency = \"TID\"\nquantity = 30\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"5mg\"\nfrequency = \"BID\"\nquantity = 30\n\n"
}
] |
{
"format": "toml",
"complexity": "simple",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 163
}
|
date = "2026-01-06"
patient_mrn = "MRN-259808"
rx_id = "RX-8539167"
prescriber = "Joseph Griffin"
[[medications]]
name = "Atorvastatin"
dosage = "10mg"
frequency = "daily"
quantity = 90
[[medications]]
name = "Lisinopril"
dosage = "10mg"
frequency = "TID"
quantity = 30
[[medications]]
name = "Metformin"
dosage = "5mg"
frequency = "BID"
quantity = 30
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id: ART-8221745\nheadline: Polarized zero administration support\nauthor: Maria Johnson\npublished: '2026-01-03T08:37:58.870132'\nsection: Business\ncontent: 'Would movement white military what them cup. Available remember control\n staff. None mean hundred PM.\n\n Improve wear produce price according. He method market computer TV strategy.\n\n Body into language. Which other hear they look some option.'\ntags:\n- environment\n- name\n- receive\n- happen\n- join\nviews: 46852\nshares: 763\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 199
}
|
article_id: ART-8221745
headline: Polarized zero administration support
author: Maria Johnson
published: '2026-01-03T08:37:58.870132'
section: Business
content: 'Would movement white military what them cup. Available remember control
staff. None mean hundred PM.
Improve wear produce price according. He method market computer TV strategy.
Body into language. Which other hear they look some option.'
tags:
- environment
- name
- receive
- happen
- join
views: 46852
shares: 763
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate contract data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-457828</contract_id>\n<effective_date>2026-01-01</effective_date>\n<term_months>32</term_months>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 120
}
|
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-457828</contract_id>
<effective_date>2026-01-01</effective_date>
<term_months>32</term_months>
</contract>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-3305496\"\npatient_mrn = \"MRN-551064\"\nprescriber = \"Eric Jackson\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"20mg\"\nfrequency = \"daily\"\nquantity = 90\n\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 119
}
|
rx_id = "RX-3305496"
patient_mrn = "MRN-551064"
prescriber = "Eric Jackson"
date = "2026-01-03"
[[medications]]
name = "Atorvastatin"
dosage = "20mg"
frequency = "daily"
quantity = 90
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"value\": 911148,\n \"contract_id\": \"CTR-919818\",\n \"parties\": [\n {\n \"name\": \"Riggs, Carey and Rojas\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Mcdowell-Koch\",\n \"role\": \"party_b\"\n }\n ],\n \"status\": \"active\",\n \"term_months\": 18\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 142
}
|
{
"value": 911148,
"contract_id": "CTR-919818",
"parties": [
{
"name": "Riggs, Carey and Rojas",
"role": "party_a"
},
{
"name": "Mcdowell-Koch",
"role": "party_b"
}
],
"status": "active",
"term_months": 18
}
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate research paper data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npaper_id = \"arXiv:2020.10600\"\ntitle = \"Reactive bi-directional middleware\"\nabstract = \"Carry prove certain tell event break. Thus not actually teacher girl perhaps.\"\nkeywords = [ \"public\", \"stock\", \"student\", \"hair\", \"hard\",]\ncitations = 273\nfunding_source = \"Salazar, Mullen and Johnson\"\n[[authors]]\nname = \"Sarah Rose\"\naffiliation = \"Martin, Taylor and Mills\"\nemail = \"adrianporter@example.com\"\n\n[[authors]]\nname = \"Samantha Garcia\"\naffiliation = \"Santiago LLC\"\nemail = \"cbrewer@example.net\"\n\n[publication]\nvenue = \"Cell\"\nyear = 2022\ndoi = \"10.6112/KodW\"\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 213
}
|
paper_id = "arXiv:2020.10600"
title = "Reactive bi-directional middleware"
abstract = "Carry prove certain tell event break. Thus not actually teacher girl perhaps."
keywords = [ "public", "stock", "student", "hair", "hard",]
citations = 273
funding_source = "Salazar, Mullen and Johnson"
[[authors]]
name = "Sarah Rose"
affiliation = "Martin, Taylor and Mills"
email = "adrianporter@example.com"
[[authors]]
name = "Samantha Garcia"
affiliation = "Santiago LLC"
email = "cbrewer@example.net"
[publication]
venue = "Cell"
year = 2022
doi = "10.6112/KodW"
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<news_article>\n<article_id>ART-2188860</article_id>\n<headline>Advanced well-modulated service-desk</headline>\n<author>Michael Logan</author>\n<published>2026-01-03T08:09:52.608144</published>\n<section>Politics</section>\n<content>Include start build no effort continue. Mention sister mention threat.\nChoose herself case writer question over. Hand quickly house send shoulder expert hour.\nAll probably suffer law consider kitchen relationship. Data population personal past security but across.</content>\n<tags>hear</tags>\n<tags>civil</tags>\n<tags>might</tags>\n<tags>way</tags>\n<tags>win</tags>\n<views>35184</views>\n<shares>1092</shares>\n</news_article>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from XML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"article_id\": \"ART-2188860\",\n \"headline\": \"Advanced well-modulated service-desk\",\n \"author\": \"Michael Logan\",\n \"published\": \"2026-01-03T08:09:52.608144\",\n \"section\": \"Politics\",\n \"content\": \"Include start build no effort continue. Mention sister mention threat.\\nChoose herself case writer question over. Hand quickly house send shoulder expert hour.\\nAll probably suffer law consider kitchen relationship. Data population personal past security but across.\",\n \"tags\": [\n \"hear\",\n \"civil\",\n \"might\",\n \"way\",\n \"win\"\n ],\n \"views\": 35184,\n \"shares\": 1092\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 224
}
|
{
"article_id": "ART-2188860",
"headline": "Advanced well-modulated service-desk",
"author": "Michael Logan",
"published": "2026-01-03T08:09:52.608144",
"section": "Politics",
"content": "Include start build no effort continue. Mention sister mention threat.\nChoose herself case writer question over. Hand quickly house send shoulder expert hour.\nAll probably suffer law consider kitchen relationship. Data population personal past security but across.",
"tags": [
"hear",
"civil",
"might",
"way",
"win"
],
"views": 35184,
"shares": 1092
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-942707\",\n \"name\": \"Organic demand-driven installation\",\n \"category\": \"books\",\n \"price\": 698.66,\n \"currency\": \"USD\",\n \"stock\": 819,\n \"is_available\": true,\n \"rating\": 4.45,\n \"reviews\": 103,\n \"specs\": {\n \"weight_kg\": 32.63,\n \"dimensions\": \"66x30x83cm\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 151
}
|
{
"product_id": "PROD-942707",
"name": "Organic demand-driven installation",
"category": "books",
"price": 698.66,
"currency": "USD",
"stock": 819,
"is_available": true,
"rating": 4.45,
"reviews": 103,
"specs": {
"weight_kg": 32.63,
"dimensions": "66x30x83cm"
}
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Transform this JSON data into XML format:\n{\n \"review_id\": \"REV-3637179\",\n \"product_id\": \"PROD-905516\",\n \"user_id\": \"cbc145e7-7f32-438c-ba90-61711bf65a15\",\n \"rating\": 1,\n \"title\": \"Hand ok join you population.\",\n \"content\": \"Develop particularly receive thing process sister source. Ago short fact start meeting note need. However music factor my million scene use.\",\n \"date\": \"2026-01-03\",\n \"verified_purchase\": false,\n \"helpful_votes\": 42\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-3637179</review_id>\n<product_id>PROD-905516</product_id>\n<user_id>cbc145e7-7f32-438c-ba90-61711bf65a15</user_id>\n<rating>1</rating>\n<title>Hand ok join you population.</title>\n<content>Develop particularly receive thing process sister source. Ago short fact start meeting note need. However music factor my million scene use.</content>\n<date>2026-01-03</date>\n<verified_purchase>False</verified_purchase>\n<helpful_votes>42</helpful_votes>\n</customer_review>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 211
}
|
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-3637179</review_id>
<product_id>PROD-905516</product_id>
<user_id>cbc145e7-7f32-438c-ba90-61711bf65a15</user_id>
<rating>1</rating>
<title>Hand ok join you population.</title>
<content>Develop particularly receive thing process sister source. Ago short fact start meeting note need. However music factor my million scene use.</content>
<date>2026-01-03</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>42</helpful_votes>
</customer_review>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output contract as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id: CTR-299234\nparties:\n- name: Murphy, Hawkins and Mckenzie\n role: party_a\n- name: Collins-Miller\n role: party_b\neffective_date: '2026-01-06'\nterm_months: 46\nvalue: 506357\nstatus: pending\n"
}
] |
{
"format": "yaml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 126
}
|
contract_id: CTR-299234
parties:
- name: Murphy, Hawkins and Mckenzie
role: party_a
- name: Collins-Miller
role: party_b
effective_date: '2026-01-06'
term_months: 46
value: 506357
status: pending
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Reformat the data below from JSON to XML:\n{\n \"level\": \"ERROR\",\n \"service\": \"writeService\",\n \"error_id\": \"85223c4c-4b76-4351-95ee-55a2460043f3\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from JSON to XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<level>ERROR</level>\n<service>writeService</service>\n<error_id>85223c4c-4b76-4351-95ee-55a2460043f3</error_id>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "simple",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 122
}
|
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<level>ERROR</level>
<service>writeService</service>
<error_id>85223c4c-4b76-4351-95ee-55a2460043f3</error_id>
</error_log>
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate course syllabus data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<course_syllabus>\n<course_id>CRS-8855</course_id>\n<code>DBP130</code>\n<title>Team-oriented 3rdgeneration implementation 101</title>\n<instructor>Carl Davis</instructor>\n<credits>3</credits>\n<term>Fall 2024</term>\n<schedule>\n<week>1</week>\n<topic>manage</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>someone</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>bring</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>board</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>important</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>he</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>possible</topic>\n</schedule>\n<schedule>\n<week>8</week>\n<topic>office</topic>\n</schedule>\n<schedule>\n<week>9</week>\n<topic>board</topic>\n</schedule>\n<schedule>\n<week>10</week>\n<topic>drive</topic>\n</schedule>\n<schedule>\n<week>11</week>\n<topic>Mrs</topic>\n</schedule>\n<grading>\n<homework>30</homework>\n<midterm>30</midterm>\n<final>40</final>\n</grading>\n</course_syllabus>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 330
}
|
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-8855</course_id>
<code>DBP130</code>
<title>Team-oriented 3rdgeneration implementation 101</title>
<instructor>Carl Davis</instructor>
<credits>3</credits>
<term>Fall 2024</term>
<schedule>
<week>1</week>
<topic>manage</topic>
</schedule>
<schedule>
<week>2</week>
<topic>someone</topic>
</schedule>
<schedule>
<week>3</week>
<topic>bring</topic>
</schedule>
<schedule>
<week>4</week>
<topic>board</topic>
</schedule>
<schedule>
<week>5</week>
<topic>important</topic>
</schedule>
<schedule>
<week>6</week>
<topic>he</topic>
</schedule>
<schedule>
<week>7</week>
<topic>possible</topic>
</schedule>
<schedule>
<week>8</week>
<topic>office</topic>
</schedule>
<schedule>
<week>9</week>
<topic>board</topic>
</schedule>
<schedule>
<week>10</week>
<topic>drive</topic>
</schedule>
<schedule>
<week>11</week>
<topic>Mrs</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate lab result data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nresult_id = \"LAB-3990665\"\npatient_mrn = \"MRN-508219\"\norder_date = \"2026-01-04\"\npanel = \"Lipid\"\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 80.7\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 90.9\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 138.0\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 131.3\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"Glucose\"\nvalue = 172.4\nunit = \"g/dL\"\nflag = \"normal\"\n\n[[results]]\ntest = \"WBC\"\nvalue = 151.6\nunit = \"g/dL\"\nflag = \"low\"\n\n[[results]]\ntest = \"Hemoglobin\"\nvalue = 188.6\nunit = \"g/dL\"\nflag = \"high\"\n\n"
}
] |
{
"format": "toml",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 223
}
|
result_id = "LAB-3990665"
patient_mrn = "MRN-508219"
order_date = "2026-01-04"
panel = "Lipid"
[[results]]
test = "Hemoglobin"
value = 80.7
unit = "g/dL"
flag = "low"
[[results]]
test = "Glucose"
value = 90.9
unit = "g/dL"
flag = "normal"
[[results]]
test = "Hemoglobin"
value = 138.0
unit = "g/dL"
flag = "low"
[[results]]
test = "WBC"
value = 131.3
unit = "g/dL"
flag = "normal"
[[results]]
test = "Glucose"
value = 172.4
unit = "g/dL"
flag = "normal"
[[results]]
test = "WBC"
value = 151.6
unit = "g/dL"
flag = "low"
[[results]]
test = "Hemoglobin"
value = 188.6
unit = "g/dL"
flag = "high"
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f</error_id>\n<timestamp>2026-01-07T13:51:25.611338</timestamp>\n<level>ERROR</level>\n<service>typeService</service>\n<message>Suggest involve part skill write left participant.</message>\n<stack_trace>at risk.py:441</stack_trace>\n<stack_trace>at strategy.py:390</stack_trace>\n<stack_trace>at performance.py:267</stack_trace>\n<stack_trace>at kind.py:265</stack_trace>\n<context>\n<user_id>3651fff2-dc6a-4fe5-a964-ed26913f3e4b</user_id>\n<request_id>f4fc48f0-6374-4e80-b666-89c2abac0904</request_id>\n</context>\n</error_log>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from XML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"error_id\": \"2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f\",\n \"timestamp\": \"2026-01-07T13:51:25.611338\",\n \"level\": \"ERROR\",\n \"service\": \"typeService\",\n \"message\": \"Suggest involve part skill write left participant.\",\n \"stack_trace\": [\n \"at risk.py:441\",\n \"at strategy.py:390\",\n \"at performance.py:267\",\n \"at kind.py:265\"\n ],\n \"context\": {\n \"user_id\": \"3651fff2-dc6a-4fe5-a964-ed26913f3e4b\",\n \"request_id\": \"f4fc48f0-6374-4e80-b666-89c2abac0904\"\n }\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 195
}
|
{
"error_id": "2a52fc1b-775b-4f0d-9bad-8f4f44e2d81f",
"timestamp": "2026-01-07T13:51:25.611338",
"level": "ERROR",
"service": "typeService",
"message": "Suggest involve part skill write left participant.",
"stack_trace": [
"at risk.py:441",
"at strategy.py:390",
"at performance.py:267",
"at kind.py:265"
],
"context": {
"user_id": "3651fff2-dc6a-4fe5-a964-ed26913f3e4b",
"request_id": "f4fc48f0-6374-4e80-b666-89c2abac0904"
}
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Output lab result as JSON."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create lab result in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"result_id\": \"LAB-5383313\",\n \"patient_mrn\": \"MRN-584871\",\n \"order_date\": \"2026-01-06\",\n \"panel\": \"CMP\",\n \"results\": [\n {\n \"test\": \"Glucose\",\n \"value\": 194.0,\n \"unit\": \"g/dL\",\n \"flag\": \"normal\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 67.1,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 195.1,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 146.6,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 119.8,\n \"unit\": \"mg/dL\",\n \"flag\": \"normal\"\n }\n ]\n}"
}
] |
{
"format": "json",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 239
}
|
{
"result_id": "LAB-5383313",
"patient_mrn": "MRN-584871",
"order_date": "2026-01-06",
"panel": "CMP",
"results": [
{
"test": "Glucose",
"value": 194.0,
"unit": "g/dL",
"flag": "normal"
},
{
"test": "Hemoglobin",
"value": 67.1,
"unit": "g/dL",
"flag": "low"
},
{
"test": "Glucose",
"value": 195.1,
"unit": "g/dL",
"flag": "low"
},
{
"test": "Hemoglobin",
"value": 146.6,
"unit": "mg/dL",
"flag": "high"
},
{
"test": "WBC",
"value": 119.8,
"unit": "mg/dL",
"flag": "normal"
}
]
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following YAML to JSON:\narticle_id: ART-2650245\nheadline: Enhanced multimedia hub\nauthor: Jennifer Davis\npublished: '2026-01-02T17:44:08.333575'\nsection: Tech\ncontent: 'Late situation both data share market. These foot health box.\n\n Pay me together western ever story cup. Game production million happy reveal. Attorney\n bill shake crime eat finally drive.\n\n Choice four concern cold test. Road executive policy official season increase.'\ntags:\n- future\n- here\n- new\nviews: 46115\nshares: 2819\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert news article from YAML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"article_id\": \"ART-2650245\",\n \"headline\": \"Enhanced multimedia hub\",\n \"author\": \"Jennifer Davis\",\n \"published\": \"2026-01-02T17:44:08.333575\",\n \"section\": \"Tech\",\n \"content\": \"Late situation both data share market. These foot health box.\\nPay me together western ever story cup. Game production million happy reveal. Attorney bill shake crime eat finally drive.\\nChoice four concern cold test. Road executive policy official season increase.\",\n \"tags\": [\n \"future\",\n \"here\",\n \"new\"\n ],\n \"views\": 46115,\n \"shares\": 2819\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "news_article",
"type": "conversion",
"estimated_tokens": 214
}
|
{
"article_id": "ART-2650245",
"headline": "Enhanced multimedia hub",
"author": "Jennifer Davis",
"published": "2026-01-02T17:44:08.333575",
"section": "Tech",
"content": "Late situation both data share market. These foot health box.\nPay me together western ever story cup. Game production million happy reveal. Attorney bill shake crime eat finally drive.\nChoice four concern cold test. Road executive policy official season increase.",
"tags": [
"future",
"here",
"new"
],
"views": 46115,
"shares": 2819
}
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output error log as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in YAML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nmessage: Baby inside high our should character study quickly.\nstack_trace:\n- at standard.py:486\n- at memory.py:53\n- at team.py:342\ncontext:\n user_id: b89e754b-fd03-47c7-9600-09a7cb6d3517\n request_id: 0aea7b7e-f431-4209-a4db-008320d27043\ntimestamp: '2026-01-07T13:51:25.507604'\n"
}
] |
{
"format": "yaml",
"complexity": "simple",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 147
}
|
message: Baby inside high our should character study quickly.
stack_trace:
- at standard.py:486
- at memory.py:53
- at team.py:342
context:
user_id: b89e754b-fd03-47c7-9600-09a7cb6d3517
request_id: 0aea7b7e-f431-4209-a4db-008320d27043
timestamp: '2026-01-07T13:51:25.507604'
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in XML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<contract>\n<contract_id>CTR-299234</contract_id>\n<parties>\n<name>Murphy, Hawkins and Mckenzie</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Collins-Miller</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-06</effective_date>\n<term_months>46</term_months>\n<value>506357</value>\n<status>pending</status>\n</contract>"
}
] |
{
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 169
}
|
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-299234</contract_id>
<parties>
<name>Murphy, Hawkins and Mckenzie</name>
<role>party_a</role>
</parties>
<parties>
<name>Collins-Miller</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-06</effective_date>
<term_months>46</term_months>
<value>506357</value>
<status>pending</status>
</contract>
|
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate social media post data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\npost_id = \"POST-49469407\"\nplatform = \"instagram\"\nuser_id = \"c776cd7c-2538-4c81-83c8-03afd724bed1\"\nusername = \"donald18\"\ncontent = \"Knowledge between friend wife property kid out. Trouble recent member sort arrive foot space good.\"\ntimestamp = \"2026-01-07T13:51:26.031233\"\nhashtags = [ \"#daughter\", \"#after\", \"#affect\", \"#goal\",]\n\n[engagement]\nlikes = 2564\nshares = 187\ncomments = 95\n"
}
] |
{
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 170
}
|
post_id = "POST-49469407"
platform = "instagram"
user_id = "c776cd7c-2538-4c81-83c8-03afd724bed1"
username = "donald18"
content = "Knowledge between friend wife property kid out. Trouble recent member sort arrive foot space good."
timestamp = "2026-01-07T13:51:26.031233"
hashtags = [ "#daughter", "#after", "#affect", "#goal",]
[engagement]
likes = 2564
shares = 187
comments = 95
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"specs\": {\n \"weight_kg\": 41.33,\n \"dimensions\": \"19x24x69cm\"\n },\n \"price\": 743.81,\n \"is_available\": true,\n \"rating\": 2.69,\n \"stock\": 485\n}"
}
] |
{
"format": "json",
"complexity": "simple",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 117
}
|
{
"specs": {
"weight_kg": 41.33,
"dimensions": "19x24x69cm"
},
"price": 743.81,
"is_available": true,
"rating": 2.69,
"stock": 485
}
|
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"contract_id\": \"CTR-274282\",\n \"parties\": [\n {\n \"name\": \"Schroeder LLC\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Kemp-Jones\",\n \"role\": \"party_b\"\n }\n ],\n \"effective_date\": \"2026-01-01\",\n \"term_months\": 28,\n \"value\": 285721,\n \"status\": \"active\"\n}"
}
] |
{
"format": "json",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 146
}
|
{
"contract_id": "CTR-274282",
"parties": [
{
"name": "Schroeder LLC",
"role": "party_a"
},
{
"name": "Kemp-Jones",
"role": "party_b"
}
],
"effective_date": "2026-01-01",
"term_months": 28,
"value": 285721,
"status": "active"
}
|
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Convert the following JSON to XML:\n{\n \"error_id\": \"249c5a8d-effc-4f5a-9a18-79860cd86eba\",\n \"timestamp\": \"2026-01-07T13:51:25.844189\",\n \"level\": \"CRITICAL\",\n \"service\": \"createService\",\n \"message\": \"Capital carry as agree member lead one.\",\n \"stack_trace\": [\n \"at sign.py:359\",\n \"at college.py:115\",\n \"at try.py:133\"\n ],\n \"context\": {\n \"user_id\": \"e110a198-5d8a-4242-b2e4-6ec6ae49ca80\",\n \"request_id\": \"939e8b37-2ce6-4ba0-bde6-ca285c8d396c\"\n }\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log from JSON to XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<error_log>\n<error_id>249c5a8d-effc-4f5a-9a18-79860cd86eba</error_id>\n<timestamp>2026-01-07T13:51:25.844189</timestamp>\n<level>CRITICAL</level>\n<service>createService</service>\n<message>Capital carry as agree member lead one.</message>\n<stack_trace>at sign.py:359</stack_trace>\n<stack_trace>at college.py:115</stack_trace>\n<stack_trace>at try.py:133</stack_trace>\n<context>\n<user_id>e110a198-5d8a-4242-b2e4-6ec6ae49ca80</user_id>\n<request_id>939e8b37-2ce6-4ba0-bde6-ca285c8d396c</request_id>\n</context>\n</error_log>"
}
] |
{
"format": "xml",
"complexity": "medium",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 215
}
|
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>249c5a8d-effc-4f5a-9a18-79860cd86eba</error_id>
<timestamp>2026-01-07T13:51:25.844189</timestamp>
<level>CRITICAL</level>
<service>createService</service>
<message>Capital carry as agree member lead one.</message>
<stack_trace>at sign.py:359</stack_trace>
<stack_trace>at college.py:115</stack_trace>
<stack_trace>at try.py:133</stack_trace>
<context>
<user_id>e110a198-5d8a-4242-b2e4-6ec6ae49ca80</user_id>
<request_id>939e8b37-2ce6-4ba0-bde6-ca285c8d396c</request_id>
</context>
</error_log>
|
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Generate sales analytics data in YAML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nperiod: September 2024\ntotal_revenue: 6726526\nunits_sold: 45392\nchannels:\n- name: retail\n revenue: 2051641\n growth: 15.93\n- name: wholesale\n revenue: 4340607\n growth: -6.59\ntop_products:\n- sku: SKU-7798\n sales: 367269\n- sku: SKU-2105\n sales: 291023\n- sku: SKU-5730\n sales: 275348\n"
}
] |
{
"format": "yaml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 149
}
|
period: September 2024
total_revenue: 6726526
units_sold: 45392
channels:
- name: retail
revenue: 2051641
growth: 15.93
- name: wholesale
revenue: 4340607
growth: -6.59
top_products:
- sku: SKU-7798
sales: 367269
- sku: SKU-2105
sales: 291023
- sku: SKU-5730
sales: 275348
|
End of preview. Expand
in Data Studio
structured_data_with_cot_dataset
このデータセットは、様々な形式（JSON、XML、YAML、TOML、CSV）の構造化データと、それぞれに対応する簡潔な思考連鎖（Chain-of-Thought, CoT）推論を含む多様な例を提供します。このデータセットの目的は、自然言語プロンプトに基づいて構造化データを生成できるモデルに対し、CoTを活用してより良い推論と出力品質を達成するための高品質な学習例を提供することです。
データセットの概要
データセットの各エントリには、以下のものが含まれます。
messages: OpenAIチャット形式に従ったメッセージ辞書のリストで、以下で構成されます。systemメッセージ: 特定のデータ形式の専門家としてのコンテキストを設定します。userメッセージ: 特定のスキーマと形式で構造化データの生成を要求するプロンプトです。多様なプロンプトテンプレートが使用されています。assistantメッセージ: 生成された構造化データに続く思考連鎖（CoT）推論が含まれます。
metadata: 例に関する追加情報で、以下が含まれます。format: 構造化データの形式（例: 'json'、'xml'、'yaml'、'toml'、'csv'）。complexity: 生成されたスキーマの複雑度（'simple'、'medium'、'complex'）。より複雑な例が多く含まれるように調整されています。schema: 表現される実世界のスキーマの種類（例: 'research_paper'、'clinical_note'、'api_specification'）。estimated_tokens: アシスタントの応答のトークン数の推定値。
サポートされるデータ形式
- JSON (JavaScript Object Notation)
- XML (Extensible Markup Language)
- YAML (YAML Ain't Markup Language)
- TOML (Tom's Obvious, Minimal Language) - 複雑なネストは簡素化される場合があります。
- CSV (Comma Separated Values) - 複数の行が生成され、フラット化された形式で表現されます。
サポートされるスキーマ
このデータセットは、以下を含む幅広いコンパクトなスキーマをカバーしています。
- 研究論文 (例:
funding_sourceのような条件付きフィールドを含む) - 実験結果
- 診療記録
- 検査結果
- 処方箋
- 契約書
- 財務報告書
- 販売分析
- API仕様
- エラーログ
- 製品リスト (例:
is_availableのような条件付きフィールドを含む) - 顧客レビュー
- 取引記録
- シラバス
- 学生評価
- ニュース記事
- ソーシャルメディア投稿
思考連鎖（Chain-of-Thought, CoT）推論
各assistantメッセージは、構造化データを生成するために取られたステップを概説する短いCoT推論ブロックから始まります。これにより、モデルは構造化データ生成に関わる論理と制約を理解し、正確で文脈に関連する出力を生成する能力を向上させることができます。CoTには、タスク、複雑度、形式ルール、構造、フィールドへのデータ入力に関する一般的なステップが含まれます。
データセットの読み込み方法
このデータセットはJSONL（JSON Lines）形式で提供されています。Hugging Faceのdatasetsライブラリを使用して簡単にロードできます。
from datasets import load_dataset
# ローカルのJSONLファイルからデータセットをロード
dataset = load_dataset('json', data_files='structured_data_with_cot_dataset.jsonl', split='train')
# 例にアクセス
print(dataset[0])
# このデータセットをHugging Face Hubにプッシュすることもできます
# from huggingface_hub import notebook_login
# notebook_login() # ログインしていない場合
# dataset.push_to_hub("your-username/structured_data_with_cot_dataset")
生成方法
このデータセットは、Fakerライブラリを活用したPythonスクリプトを使用して、様々なコンパクトなスキーマに対して現実的な構造化データを生成しました。生成プロセスには、スキーマ、形式、複雑度をランダムに選択し、思考連鎖推論を埋め込むロジックが含まれており、大規模言語モデルのトレーニングに適した多様性と品質を保証します。特に、より多様なプロンプトテンプレートが使用され、データセットの複雑度の分布が調整され（より多くの「medium」および「complex」な例）、いくつかのスキーマジェネレーターには条件付きフィールド（例：研究論文の資金源、製品リストの在庫状況）や、CSVの動的な複数行生成ロジックが追加されています。TOML変換は、TOMLの仕様に合わせてネストされた構造を簡素化する場合があります。
- Downloads last month
- 20
Size of downloaded dataset files:
1.84 MB
Size of the auto-converted Parquet files:
1.84 MB
Number of rows:
3,386