messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"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: 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: e23a799e-7aa9-472f-8af5-afafc677007a\ntimestamp: '2026-01-07T01:26:12.058954'\nlevel: WARNING\nservice: growService\nmessage: Defense this center.\nstack_trace:\n- at them.py:204\n- at soon.py:149\n- at edge.py:145\ncontext:\n user_id: 2bd3ece4-6e4c-479a-ae96-c11d2854e4e4\n request_id: bf4cdcaa-d8b0-4c5d-985d-53d20e43beda\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\ncontent,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username\r\nFloor economy pass attack find over hear. Down cold action approach soldier blood realize. Southern ,95,3161,550,\"[\"\"#difference\"\", \"\"#receive\"\", \"\"#mention\"\"]\",instagram,POST-65150556,2026-01-07T01:26:15.127785,04a61c2c-797a-4c85-8a2a-b84176aa6aca,rachel74\r\n\"Expert evidence family memory.\nNecessary wear recent today great time. Adult require draw fish also \",133,878,552,\"[\"\"#first\"\", \"\"#of\"\", \"\"#administration\"\"]\",facebook,POST-51933522,2026-01-07T01:26:15.137594,8e556357-2ec6-4f7d-a188-56db0a0f2f18,lsanders\r\nLight either start assume. Affect happen summer take the early. Well skin member trouble factor.,361,1973,331,\"[\"\"#other\"\", \"\"#once\"\", \"\"#find\"\"]\",twitter,POST-46948836,2026-01-07T01:26:15.138173,d59ee33f-e962-44ec-9f08-3b38d18c37b1,holmeswilliam\r\n\"Reveal officer tonight doctor minute lot main. Idea soon identify to.\nNotice else political move lik\",197,3739,152,\"[\"\"#station\"\", \"\"#attack\"\", \"\"#writer\"\"]\",facebook,POST-38482044,2026-01-07T01:26:15.138534,fa342611-d3e3-4f45-81bc-d9bf80294968,bmontgomery\r\n\"Reach half create before impact once. Firm game international.\nSong issue accept stop high tough. Qu\",171,7303,120,\"[\"\"#use\"\", \"\"#cover\"\"]\",twitter,POST-77630142,2026-01-07T01:26:15.139013,8c017398-3bf8-4211-87c7-3ac9bb1eb985,bellroger\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from CSV to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"post_id\": \"POST-65150556\",\n \"platform\": \"instagram\",\n \"user_id\": \"04a61c2c-797a-4c85-8a2a-b84176aa6aca\",\n \"username\": \"rachel74\",\n \"content\": \"Floor economy pass attack find over hear. Down cold action approach soldier blood realize. Southern action skill none accept full develop. Else reveal hand another.\",\n \"timestamp\": \"2026-01-07T01:26:15.127785\",\n \"hashtags\": [\n \"#difference\",\n \"#receive\",\n \"#mention\"\n ],\n \"engagement\": {\n \"likes\": 3161,\n \"shares\": 550,\n \"comments\": 95\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 208
} |
[
{
"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 social media post."
},
{
"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-82648479\"\nplatform = \"facebook\"\nuser_id = \"2ce65273-8398-49af-9ef3-c7aac18b44c5\"\nusername = \"christopherking\"\ncontent = \"Rich strong drop argue common letter. Everything radio benefit marriage respond maintain. Land seem old budget during.\"\ntimestamp = \"2026-01-07T01:26:10.639400\"\nhashtags = [ \"#physical\", \"#PM\",]\n\n[engagement]\nlikes = 5016\nshares = 272\ncomments = 496\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 171
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id: RX-3966060\npatient_mrn: MRN-866595\nprescriber: Vanessa Hull\ndate: '2026-01-06'\nmedications:\n- name: Lisinopril\n dosage: 5mg\n frequency: daily\n quantity: 30\n- name: Metformin\n dosage: 10mg\n frequency: daily\n quantity: 30\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 135
} |
[
{
"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 student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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:\nassessment_id: ASMT-788951\nstudent_id: STU-569359\ncourse_id: CRS-7653\ntype: assignment\ndate: '2026-01-02'\nscores:\n- question: 1\n points_earned: 1\n points_possible: 10\n- question: 2\n points_earned: 5\n points_possible: 10\n- question: 3\n points_earned: 5\n points_possible: 10\n- question: 4\n points_earned: 7\n points_possible: 10\n- question: 5\n points_earned: 6\n points_possible: 10\n- question: 6\n points_earned: 5\n points_possible: 10\n- question: 7\n points_earned: 5\n points_possible: 10\n- question: 8\n points_earned: 10\n points_possible: 10\n- question: 9\n points_earned: 8\n points_possible: 10\n- question: 10\n points_earned: 8\n points_possible: 10\n- question: 11\n points_earned: 4\n points_possible: 10\n- question: 12\n points_earned: 3\n points_possible: 10\ntotal_score: 92\npercentage: 90.32\ngrade: B\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 283
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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:\nnote_id = \"CN-6460542\"\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"I93\"\n\n[vitals]\nbp = \"164/68\"\nhr = 64\ntemp_f = 99.7\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 104
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output course syllabus as YAML."
},
{
"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:\ncourse_id: CRS-4631\nschedule:\n- week: 1\n topic: certainly\n- week: 2\n topic: night\n- week: 3\n topic: treatment\n- week: 4\n topic: realize\n- week: 5\n topic: box\n- week: 6\n topic: senior\n- week: 7\n topic: receive\n- week: 8\n topic: will\n- week: 9\n topic: shake\n- week: 10\n topic: follow\n- week: 11\n topic: vote\ncredits: 3\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 173
} |
[
{
"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 social media post."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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:\npost_id: POST-89350344\nplatform: instagram\nuser_id: 177d26a1-e40d-40fb-8b8b-f4b79cd11dcf\nusername: marcia86\ncontent: When sea magazine office responsibility build company tell. Always reveal\n training career message food try. Above ask and since.\ntimestamp: '2026-01-07T01:26:11.263488'\nhashtags:\n- '#money'\n- '#activity'\n- '#have'\n- '#rule'\nengagement:\n likes: 2467\n shares: 369\n comments: 343\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 178
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "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>Fully-configurable explicit success API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</behavior>\n<get>\n<summary>Watch bar meeting success director.</summary>\n<parameters>\n<name>param0</name>\n<in>query</in>\n<type>string</type>\n</parameters>\n<responses>\n<200>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//behavior>\n</paths>\n</api_specification>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert api specification 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 \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Fully-configurable explicit success API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/behavior\": {\n \"get\": {\n \"summary\": \"Watch bar meeting success director.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "conversion",
"estimated_tokens": 220
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Generate contract data in TOML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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:\ncontract_id = \"CTR-177284\"\neffective_date = \"2026-01-01\"\nterm_months = 48\nvalue = 886350\nstatus = \"executed\"\n[[parties]]\nname = \"Adams, Strickland and Thompson\"\nrole = \"party_a\"\n\n[[parties]]\nname = \"Reeves LLC\"\nrole = \"party_b\"\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 129
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output clinical note as XML."
},
{
"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-5728813</note_id>\n<patient>\n<mrn>MRN-497146</mrn>\n<age>46</age>\n<gender>M</gender>\n</patient>\n<encounter_date>2026-01-05</encounter_date>\n<chief_complaint>headache</chief_complaint>\n<vitals>\n<bp>118/97</bp>\n<hr>66</hr>\n<temp_f>97.8</temp_f>\n</vitals>\n<assessment>\n<problem>hypertension</problem>\n<icd10>J47</icd10>\n</assessment>\n</clinical_note>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 179
} |
[
{
"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 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\": \"Team-oriented client-driven contingency API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/section\": {\n \"get\": {\n \"summary\": \"Wait area whole alone affect gun process.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 276
} |
[
{
"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 contract."
},
{
"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<status>active</status>\n<contract_id>CTR-272020</contract_id>\n<effective_date>2026-01-03</effective_date>\n<parties>\n<name>Green-Williams</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Richardson, Osborne and Sawyer</name>\n<role>party_b</role>\n</parties>\n</contract>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "generation",
"estimated_tokens": 157
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output social media post as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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<social_media_post>\n<post_id>POST-82648479</post_id>\n<platform>facebook</platform>\n<user_id>2ce65273-8398-49af-9ef3-c7aac18b44c5</user_id>\n<username>christopherking</username>\n<content>Rich strong drop argue common letter. Everything radio benefit marriage respond maintain. Land seem old budget during.</content>\n<timestamp>2026-01-07T01:26:10.639400</timestamp>\n<hashtags>#physical</hashtags>\n<hashtags>#PM</hashtags>\n<engagement>\n<likes>5016</likes>\n<shares>272</shares>\n<comments>496</comments>\n</engagement>\n</social_media_post>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 220
} |
[
{
"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:\npaper_id: arXiv:2020.19242\ntitle: Enhanced fresh-thinking pricing structure\nauthors:\n- name: Shannon Calderon\n affiliation: Hardy, Ramos and Schneider\n email: carolyn21@example.net\n- name: April Cook\n affiliation: Medina, Nielsen and Perkins\n email: wadekyle@example.com\nabstract: Others senior until relationship follow tree. See other off fly form. Economy\n third free relate.\nkeywords:\n- foreign\n- able\n- south\n- bar\npublication:\n venue: Cell\n year: 2023\n doi: 10.2523/QzEC\ncitations: 379\nfunding_source: Thomas-Warren\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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 \"paper_id\": \"arXiv:2020.19242\",\n \"title\": \"Enhanced fresh-thinking pricing structure\",\n \"authors\": [\n {\n \"name\": \"Shannon Calderon\",\n \"affiliation\": \"Hardy, Ramos and Schneider\",\n \"email\": \"carolyn21@example.net\"\n },\n {\n \"name\": \"April Cook\",\n \"affiliation\": \"Medina, Nielsen and Perkins\",\n \"email\": \"wadekyle@example.com\"\n }\n ],\n \"abstract\": \"Others senior until relationship follow tree. See other off fly form. Economy third free relate.\",\n \"keywords\": [\n \"foreign\",\n \"able\",\n \"south\",\n \"bar\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2023,\n \"doi\": \"10.2523/QzEC\"\n },\n \"citations\": 379,\n \"funding_source\": \"Thomas-Warren\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 257
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from YAML to JSON:\nreview_id: REV-1677003\nproduct_id: PROD-392709\nuser_id: fedb70b5-ea85-4d21-a9fe-87d61e742d40\nrating: 2\ntitle: Discussion any glass make once.\ncontent: Trial out use design baby. Appear investment concern plan. Cover career door\n instead year. Yeah candidate continue none.\ndate: '2026-01-01'\nverified_purchase: false\nhelpful_votes: 77\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review from YAML to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"review_id\": \"REV-1677003\",\n \"product_id\": \"PROD-392709\",\n \"user_id\": \"fedb70b5-ea85-4d21-a9fe-87d61e742d40\",\n \"rating\": 2,\n \"title\": \"Discussion any glass make once.\",\n \"content\": \"Trial out use design baby. Appear investment concern plan. Cover career door instead year. Yeah candidate continue none.\",\n \"date\": \"2026-01-01\",\n \"verified_purchase\": false,\n \"helpful_votes\": 77\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 177
} |
[
{
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncourse_id = \"CRS-6754\"\ncode = \"NGM306\"\ntitle = \"User-centric bottom-line Local Area Network 101\"\ninstructor = \"Shannon Gonzalez\"\ncredits = 3\nterm = \"Spring 2020\"\n[[schedule]]\nweek = 1\ntopic = \"much\"\n\n[[schedule]]\nweek = 2\ntopic = \"little\"\n\n[[schedule]]\nweek = 3\ntopic = \"station\"\n\n[[schedule]]\nweek = 4\ntopic = \"call\"\n\n[[schedule]]\nweek = 5\ntopic = \"watch\"\n\n[[schedule]]\nweek = 6\ntopic = \"close\"\n\n[[schedule]]\nweek = 7\ntopic = \"mention\"\n\n[[schedule]]\nweek = 8\ntopic = \"direction\"\n\n[[schedule]]\nweek = 9\ntopic = \"study\"\n\n[[schedule]]\nweek = 10\ntopic = \"analysis\"\n\n[[schedule]]\nweek = 11\ntopic = \"discuss\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 238
} |
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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 \"txn_id\": \"TXN-84895707\",\n \"customer_id\": \"cf005a78-41f9-4c51-acfb-22dfdae035d7\",\n \"timestamp\": \"2026-01-07T01:26:13.967358\",\n \"items\": [\n {\n \"sku\": \"SKU-47868\",\n \"qty\": 1,\n \"price\": 193.12\n }\n ],\n \"subtotal\": 396.74,\n \"tax\": 104.18,\n \"total\": 354.16,\n \"payment_method\": \"apple_pay\"\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 158
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of product listing."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"product_id\": \"PROD-229836\",\n \"name\": \"Ameliorated foreground throughput\",\n \"category\": \"electronics\",\n \"price\": 705.83,\n \"currency\": \"USD\",\n \"stock\": 311,\n \"is_available\": true,\n \"rating\": 1.0,\n \"reviews\": 500,\n \"specs\": {\n \"weight_kg\": 40.38,\n \"dimensions\": \"82x42x85cm\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 152
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "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\": \"November 2024\",\n \"total_revenue\": 2676189,\n \"units_sold\": 83309,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 3563016,\n \"growth\": 23.93\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 4310802,\n \"growth\": 22.7\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-6301\",\n \"sales\": 28890\n },\n {\n \"sku\": \"SKU-7925\",\n \"sales\": 186307\n },\n {\n \"sku\": \"SKU-7802\",\n \"sales\": 163007\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Produce a JSON document for a student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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 \"assessment_id\": \"ASMT-753971\",\n \"student_id\": \"STU-150372\",\n \"course_id\": \"CRS-3280\",\n \"type\": \"assignment\",\n \"date\": \"2026-01-04\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 6,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 4,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 5,\n \"points_earned\": 1,\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\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 4,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 64,\n \"percentage\": 66.83,\n \"grade\": \"B\"\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 331
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output prescription as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription 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<prescription>\n<rx_id>RX-2110944</rx_id>\n<patient_mrn>MRN-267033</patient_mrn>\n<prescriber>Paul Ellis</prescriber>\n<date>2026-01-02</date>\n<medications>\n<name>Atorvastatin</name>\n<dosage>20mg</dosage>\n<frequency>TID</frequency>\n<quantity>30</quantity>\n</medications>\n<medications>\n<name>Atorvastatin</name>\n<dosage>20mg</dosage>\n<frequency>BID</frequency>\n<quantity>90</quantity>\n</medications>\n<medications>\n<name>Lisinopril</name>\n<dosage>10mg</dosage>\n<frequency>daily</frequency>\n<quantity>60</quantity>\n</medications>\n</prescription>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 220
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<customer_review>\n<review_id>REV-1957111</review_id>\n<product_id>PROD-201304</product_id>\n<user_id>b93fcf3a-3e21-4cfa-853d-b66c43f2103b</user_id>\n<rating>2</rating>\n<title>Suggest her us identify phone both pressure produc</title>\n<content>Majority station however visit daughter court.\nCivil wrong similar series bed. Stage dog themselves sure direction.\nGas dog reach every among brother ask everybody.</content>\n<date>2026-01-04</date>\n<verified_purchase>True</verified_purchase>\n<helpful_votes>9</helpful_votes>\n</customer_review>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert customer review 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:\nreview_id: REV-1957111\nproduct_id: PROD-201304\nuser_id: b93fcf3a-3e21-4cfa-853d-b66c43f2103b\nrating: 2\ntitle: Suggest her us identify phone both pressure produc\ncontent: 'Majority station however visit daughter court.\n\n Civil wrong similar series bed. Stage dog themselves sure direction.\n\n Gas dog reach every among brother ask everybody.'\ndate: '2026-01-04'\nverified_purchase: true\nhelpful_votes: 9\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "customer_review",
"type": "conversion",
"estimated_tokens": 179
} |
[
{
"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: 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>July 2024</period>\n<total_revenue>3830731</total_revenue>\n<units_sold>4114</units_sold>\n<channels>\n<name>retail</name>\n<revenue>3962653</revenue>\n<growth>41.57</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>752149</revenue>\n<growth>37.04</growth>\n</channels>\n<top_products>\n<sku>SKU-3410</sku>\n<sales>244103</sales>\n</top_products>\n<top_products>\n<sku>SKU-3961</sku>\n<sales>282902</sales>\n</top_products>\n<top_products>\n<sku>SKU-2630</sku>\n<sales>263402</sales>\n</top_products>\n</sales_analytics>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 222
} |
[
{
"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-6025536\npatient_mrn: MRN-762507\nprescriber: Rebecca Park\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": 118
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output prescription as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ndate,medications,patient_mrn,prescriber,rx_id\r\n2026-01-06,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 60}, {\"\"name\"\": \"\"Metformin\"\"\",MRN-901842,Jerome Miller,RX-2341215\r\n2026-01-05,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"10mg\"\", \"\"frequency\"\": \"\"TID\"\", \"\"quantity\"\": 60}, {\"\"name\"\": \"\"Metformin\"\",\",MRN-608794,Kenneth Montoya,RX-9042010\r\n2026-01-05,\"[{\"\"name\"\": \"\"Atorvastatin\"\", \"\"dosage\"\": \"\"5mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 90}, {\"\"name\"\": \"\"Lisinopril\",MRN-411703,Lawrence Gordon,RX-2020595\r\n2026-01-03,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"BID\"\", \"\"quantity\"\": 90}]\",MRN-525201,Shawn Porter,RX-3273918\r\n2026-01-06,\"[{\"\"name\"\": \"\"Lisinopril\"\", \"\"dosage\"\": \"\"20mg\"\", \"\"frequency\"\": \"\"daily\"\", \"\"quantity\"\": 60}, {\"\"name\"\": \"\"Metformin\",MRN-811317,Adam Flores,RX-6989694\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 293
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Create a CSV representation of student assessment."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\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-252485,,CRS-4065,,2026-01-02,A,,,,,70.41,,\"[{\"\"question\"\": 1, \"\"points_earned\"\": 10, \"\"points_possible\"\": 10}, {\"\"question\"\": 2, \"\"points_earned\"\": 4, \"\"p\",STU-873113,,,87,assignment\r\n,EWG101,CRS-9548,3,,,40,30,30,Craig Allen PhD,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"military\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"major\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"reason\"\"}, {\"\"\",,,Fall 2020,Monitored actuating info-mediaries 101,,\r\n,GEU307,CRS-2566,4,,,40,30,30,Jennifer Mcfarland,,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"product\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"real\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"yet\"\"}, {\"\"week\"\"\",,,Spring 2024,Programmable full-range middleware 101,,\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 281
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output transaction record as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ntxn_id: TXN-29317468\ncustomer_id: 32de661e-5c6c-4668-a764-468f8a660652\ntimestamp: '2026-01-07T01:26:13.365116'\nitems:\n- sku: SKU-90938\n qty: 5\n price: 76.11\nsubtotal: 847.54\ntax: 125.13\ntotal: 1787.23\npayment_method: paypal\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 135
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<research_paper>\n<paper_id>arXiv:2021.87440</paper_id>\n<title>Re-contextualized discrete interface</title>\n<authors>\n<name>Timothy Bass</name>\n<affiliation>Clark-Fisher</affiliation>\n<email>jamie52@example.net</email>\n</authors>\n<authors>\n<name>Paul Fisher</name>\n<affiliation>Wilkins-Oconnell</affiliation>\n<email>nicolemills@example.net</email>\n</authors>\n<abstract>We realize sing laugh room wish boy. Look physical movement prevent stuff very real draw.</abstract>\n<keywords>family</keywords>\n<keywords>develop</keywords>\n<keywords>strong</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2021</year>\n<doi>10.5535/teRG</doi>\n</publication>\n<citations>288</citations>\n<funding_source>Diaz-Smith</funding_source>\n</research_paper>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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:\npaper_id: arXiv:2021.87440\ntitle: Re-contextualized discrete interface\nauthors:\n- name: Timothy Bass\n affiliation: Clark-Fisher\n email: jamie52@example.net\n- name: Paul Fisher\n affiliation: Wilkins-Oconnell\n email: nicolemills@example.net\nabstract: We realize sing laugh room wish boy. Look physical movement prevent stuff\n very real draw.\nkeywords:\n- family\n- develop\n- strong\npublication:\n venue: Cell\n year: 2021\n doi: 10.5535/teRG\ncitations: 288\nfunding_source: Diaz-Smith\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 200
} |
[
{
"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 research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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:\ntitle = \"Optional modular intranet\"\npaper_id = \"arXiv:2024.47313\"\n\n[publication]\nvenue = \"Cell\"\nyear = 2021\ndoi = \"10.3290/Fkot\"\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 107
} |
[
{
"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 experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result 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:\nexperiment_id: EXP-910542\nresults:\n- metric: efficacy\n baseline: 16.77\n endpoint: 42.81\n p_value: 0.4331\n- metric: safety\n baseline: 42.12\n endpoint: 13.05\n p_value: 0.368\n- metric: efficacy\n baseline: 69.15\n endpoint: 76.43\n p_value: 0.4094\n- metric: efficacy\n baseline: 32.83\n endpoint: 72.69\n p_value: 0.1645\nconclusion: significant\nmethodology:\n design: cohort\n sample_size: 60\n duration_days: 120\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 183
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a error log."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log 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:\nerror_id = \"f0260cae-6cae-4d43-b5b5-a4c8ca2b288c\"\ntimestamp = \"2026-01-07T01:26:14.692399\"\nlevel = \"WARNING\"\nservice = \"bringService\"\nmessage = \"Republican media form.\"\nstack_trace = [ \"at ago.py:121\", \"at local.py:225\", \"at young.py:313\", \"at street.py:257\",]\n\n[context]\nuser_id = \"0a8b29b7-392c-4e6b-b651-35bb6e5752ec\"\nrequest_id = \"77fab727-e699-43d1-a0e0-ef65bcde87ca\"\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 166
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output api specification as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in XML\n2. Complexity: 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<api_specification>\n<openapi>3.0.0</openapi>\n<info>\n<title>Horizontal client-server migration API</title>\n<version>1.0.0</version>\n</info>\n<paths>\n</bad>\n<get>\n<summary>Expert can wish husband reduce something white.</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>{'description': 'Success'}</200>\n<400>{'description': 'Bad Request'}</400>\n</responses>\n</get>\n<//bad>\n</paths>\n</api_specification>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 222
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate research paper data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\n\"Sign bad light couple against. Boy room by travel. Democrat film spring contain.\nCapital difficult b\",\"[{\"\"name\"\": \"\"April Smith MD\"\", \"\"affiliation\"\": \"\"Brown LLC\"\", \"\"email\"\": \"\"xbrewer@example.org\"\"}, {\"\"name\"\": \"\"C\",300,Fox Ltd,\"[\"\"west\"\", \"\"hotel\"\", \"\"also\"\"]\",arXiv:2024.51874,10.9109/EQAY,Cell,2020,Advanced radical throughput\r\nNational pull explain anything including oil. Look cover rule group water before. Day enjoy water le,\"[{\"\"name\"\": \"\"Matthew Navarro\"\", \"\"affiliation\"\": \"\"Fisher-Morrison\"\", \"\"email\"\": \"\"bwallace@example.net\"\"}, {\"\"n\",320,\"Carter, Freeman and Morris\",\"[\"\"should\"\", \"\"ok\"\", \"\"money\"\", \"\"body\"\"]\",arXiv:2020.56742,10.4367/aVQo,Cell,2021,Persevering next generation encoding\r\nPattern claim enjoy choice cut rise pull. Nation by true whether. Expert eye box college senior shor,\"[{\"\"name\"\": \"\"Sara Medina\"\", \"\"affiliation\"\": \"\"Parrish Group\"\", \"\"email\"\": \"\"williamsjeffery@example.org\"\"}, {\"\"\",55,\"Harris, Perry and Hanna\",\"[\"\"somebody\"\", \"\"imagine\"\", \"\"ground\"\"]\",arXiv:2020.86132,10.7181/UjEi,Cell,2024,Horizontal radical benchmark\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 373
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output contract as XML."
},
{
"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-948938</contract_id>\n<parties>\n<name>Schneider LLC</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Henry-Potter</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-06</effective_date>\n<term_months>29</term_months>\n<value>257394</value>\n<status>active</status>\n</contract>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "contract",
"type": "generation",
"estimated_tokens": 165
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output sales analytics as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create sales analytics in TOML\n2. Complexity: 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:\nperiod = \"May 2023\"\nunits_sold = 77645\ntotal_revenue = 9019639\n[[top_products]]\nsku = \"SKU-2591\"\nsales = 401868\n\n[[top_products]]\nsku = \"SKU-8877\"\nsales = 431318\n\n[[top_products]]\nsku = \"SKU-8633\"\nsales = 323901\n\n[[channels]]\nname = \"online\"\nrevenue = 2916933\ngrowth = 1.53\n\n[[channels]]\nname = \"wholesale\"\nrevenue = 540652\ngrowth = 0.4\n\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 160
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Output experiment result as YAML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in YAML\n2. Complexity: 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:\nmethodology:\n design: observational\n sample_size: 621\n duration_days: 109\nconclusion: non-significant\ntitle: Effect of front on always\nresults:\n- metric: efficacy\n baseline: 20.32\n endpoint: 34.12\n p_value: 0.2299\n- metric: safety\n baseline: 70.2\n endpoint: 95.83\n p_value: 0.4047\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 152
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this XML data into JSON format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<student_assessment>\n<assessment_id>ASMT-828472</assessment_id>\n<student_id>STU-735131</student_id>\n<course_id>CRS-8725</course_id>\n<type>quiz</type>\n<date>2026-01-04</date>\n<scores>\n<question>1</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>4</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>9</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>0</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>8</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>9</question>\n<points_earned>5</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>10</question>\n<points_earned>7</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>67</total_score>\n<percentage>50.34</percentage>\n<grade>A</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-828472\",\n \"student_id\": \"STU-735131\",\n \"course_id\": \"CRS-8725\",\n \"type\": \"quiz\",\n \"date\": \"2026-01-04\",\n \"scores\": [\n {\n \"question\": 1,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 2,\n \"points_earned\": 10,\n \"points_possible\": 10\n },\n {\n \"question\": 3,\n \"points_earned\": 4,\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\": 9,\n \"points_possible\": 10\n },\n {\n \"question\": 6,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 7,\n \"points_earned\": 0,\n \"points_possible\": 10\n },\n {\n \"question\": 8,\n \"points_earned\": 4,\n \"points_possible\": 10\n },\n {\n \"question\": 9,\n \"points_earned\": 5,\n \"points_possible\": 10\n },\n {\n \"question\": 10,\n \"points_earned\": 7,\n \"points_possible\": 10\n },\n {\n \"question\": 11,\n \"points_earned\": 2,\n \"points_possible\": 10\n },\n {\n \"question\": 12,\n \"points_earned\": 0,\n \"points_possible\": 10\n }\n ],\n \"total_score\": 67,\n \"percentage\": 50.34,\n \"grade\": \"A\"\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "student_assessment",
"type": "conversion",
"estimated_tokens": 398
} |
[
{
"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>e87e09f8-a125-4a0e-a242-053a197e90d0</error_id>\n<timestamp>2026-01-07T01:26:15.158896</timestamp>\n<level>WARNING</level>\n<service>theoryService</service>\n<message>Bank sense us job collection.</message>\n<stack_trace>at for.py:456</stack_trace>\n<stack_trace>at your.py:112</stack_trace>\n<stack_trace>at option.py:325</stack_trace>\n<stack_trace>at politics.py:395</stack_trace>\n<context>\n<user_id>ccc14e1f-796d-4192-9716-90d81faf39e4</user_id>\n<request_id>3798d3d7-8606-4c03-8742-540c58fbf326</request_id>\n</context>\n</error_log>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 223
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in TOML\n2. Complexity: 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:\nconclusion = \"non-significant\"\nexperiment_id = \"EXP-644074\"\ntitle = \"Effect of every on minute\"\n[[results]]\nmetric = \"efficacy\"\nbaseline = 92.99\nendpoint = 88.09\np_value = 0.4524\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 77.42\nendpoint = 10.45\np_value = 0.2006\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 85.67\nendpoint = 41.19\np_value = 0.3658\n\n[[results]]\nmetric = \"safety\"\nbaseline = 31.59\nendpoint = 78.34\np_value = 0.1027\n\n[methodology]\ndesign = \"RCT\"\nsample_size = 387\nduration_days = 98\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 200
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a sales analytics."
},
{
"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>February 2020</period>\n<total_revenue>1994080</total_revenue>\n<units_sold>60128</units_sold>\n<channels>\n<name>wholesale</name>\n<revenue>1229681</revenue>\n<growth>7.48</growth>\n</channels>\n<channels>\n<name>online</name>\n<revenue>1896521</revenue>\n<growth>9.25</growth>\n</channels>\n<top_products>\n<sku>SKU-7163</sku>\n<sales>296439</sales>\n</top_products>\n<top_products>\n<sku>SKU-2876</sku>\n<sales>135590</sales>\n</top_products>\n<top_products>\n<sku>SKU-1852</sku>\n<sales>57357</sales>\n</top_products>\n</sales_analytics>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "sales_analytics",
"type": "generation",
"estimated_tokens": 223
} |
[
{
"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 \"period\": \"December 2023\",\n \"total_revenue\": 9932042,\n \"units_sold\": 13461,\n \"channels\": [\n {\n \"name\": \"retail\",\n \"revenue\": 829720,\n \"growth\": 24.62\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 1324765,\n \"growth\": 34.86\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-1872\",\n \"sales\": 424218\n },\n {\n \"sku\": \"SKU-5255\",\n \"sales\": 225860\n },\n {\n \"sku\": \"SKU-8389\",\n \"sales\": 39267\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics 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<sales_analytics>\n<period>December 2023</period>\n<total_revenue>9932042</total_revenue>\n<units_sold>13461</units_sold>\n<channels>\n<name>retail</name>\n<revenue>829720</revenue>\n<growth>24.62</growth>\n</channels>\n<channels>\n<name>wholesale</name>\n<revenue>1324765</revenue>\n<growth>34.86</growth>\n</channels>\n<top_products>\n<sku>SKU-1872</sku>\n<sales>424218</sales>\n</top_products>\n<top_products>\n<sku>SKU-5255</sku>\n<sales>225860</sales>\n</top_products>\n<top_products>\n<sku>SKU-8389</sku>\n<sales>39267</sales>\n</top_products>\n</sales_analytics>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 224
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nbooks,USD,True,Enhanced motivating open system,675.27,PROD-552338,3.21,759,68x72x17cm,35.93,10\r\nelectronics,USD,True,Organized uniform hub,807.26,PROD-202268,4.27,76,33x29x79cm,25.91,550\r\nbooks,USD,True,Adaptive discrete infrastructure,80.45,PROD-863184,4.28,981,72x69x78cm,46.14,294\r\nclothing,USD,True,Triple-buffered executive firmware,209.12,PROD-757913,2.2,42,17x49x84cm,8.6,437\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from CSV to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"product_id\": \"PROD-552338\",\n \"name\": \"Enhanced motivating open system\",\n \"category\": \"books\",\n \"price\": 675.27,\n \"currency\": \"USD\",\n \"stock\": 10,\n \"is_available\": true,\n \"rating\": 3.21,\n \"reviews\": 759,\n \"specs\": {\n \"weight_kg\": 35.93,\n \"dimensions\": \"68x72x17cm\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 151
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in TOML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nexperiment_id = \"EXP-263108\"\ntitle = \"Effect of beautiful on question\"\nconclusion = \"significant\"\n[[results]]\nmetric = \"safety\"\nbaseline = 74.44\nendpoint = 48.19\np_value = 0.3589\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 58.91\nendpoint = 28.67\np_value = 0.0823\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 15.55\nendpoint = 16.79\np_value = 0.433\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 28.02\nendpoint = 85.11\np_value = 0.2281\n\n[methodology]\ndesign = \"observational\"\nsample_size = 516\nduration_days = 270\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 201
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output research paper as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper 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<research_paper>\n<paper_id>arXiv:2022.32605</paper_id>\n<title>Cross-group bandwidth-monitored moderator</title>\n<authors>\n<name>Willie Willis</name>\n<affiliation>Cooper-Ross</affiliation>\n<email>imason@example.org</email>\n</authors>\n<authors>\n<name>Derrick Goodman</name>\n<affiliation>Jordan-Dunlap</affiliation>\n<email>robert58@example.net</email>\n</authors>\n<abstract>Discussion test argue party step. Clearly the change discussion. Summer continue certain police manage study trade.</abstract>\n<keywords>firm</keywords>\n<keywords>receive</keywords>\n<keywords>laugh</keywords>\n<keywords>price</keywords>\n<publication>\n<venue>Science</venue>\n<year>2020</year>\n<doi>10.9746/dovY</doi>\n</publication>\n<citations>469</citations>\n<funding_source />\n</research_paper>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 277
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output prescription as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: 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-1960683\"\npatient_mrn = \"MRN-613072\"\nprescriber = \"Samantha Barnett\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Atorvastatin\"\ndosage = \"5mg\"\nfrequency = \"TID\"\nquantity = 60\n\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"10mg\"\nfrequency = \"daily\"\nquantity = 60\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 141
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\nabstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold\r\n,,\"[{\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 2916933, \"\"growth\"\": 1.53}, {\"\"name\"\": \"\"wholesale\"\", \"\"revenue\"\": 540652, \"\"g\",,,,,May 2023,,,,,\"[{\"\"sku\"\": \"\"SKU-2591\"\", \"\"sales\"\": 401868}, {\"\"sku\"\": \"\"SKU-8877\"\", \"\"sales\"\": 431318}, {\"\"sku\"\": \"\"SKU-8633\"\", \"\"sa\",9019639,77645\r\n\"Former through table debate dinner citizen mother poor.\nOfficer western best long analysis try. Part\",\"[{\"\"name\"\": \"\"Jennifer Jenkins\"\", \"\"affiliation\"\": \"\"Martinez, Nielsen and Mcdonald\"\", \"\"email\"\": \"\"hhess@examp\",,132,None,\"[\"\"ready\"\", \"\"successful\"\", \"\"listen\"\", \"\"evidence\"\"]\",arXiv:2022.18056,,10.5238/cjwH,Science,2020,Advanced interactive middleware,,,\r\nGood idea discover receive world. Factor executive role amount production few.,\"[{\"\"name\"\": \"\"Molly Johnson\"\", \"\"affiliation\"\": \"\"Villarreal-Gallagher\"\", \"\"email\"\": \"\"cantudaniel@example.org\"\"\",,80,None,\"[\"\"I\"\", \"\"per\"\", \"\"ready\"\", \"\"if\"\", \"\"pressure\"\"]\",arXiv:2020.24366,,10.3659/Wfut,Nature,2020,Self-enabling reciprocal benchmark,,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from CSV to JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"period\": \"May 2023\",\n \"units_sold\": 77645,\n \"top_products\": [\n {\n \"sku\": \"SKU-2591\",\n \"sales\": 401868\n },\n {\n \"sku\": \"SKU-8877\",\n \"sales\": 431318\n },\n {\n \"sku\": \"SKU-8633\",\n \"sales\": 323901\n }\n ],\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 2916933,\n \"growth\": 1.53\n },\n {\n \"name\": \"wholesale\",\n \"revenue\": 540652,\n \"growth\": 0.4\n }\n ],\n \"total_revenue\": 9019639\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 197
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Create a TOML representation of news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id = \"ART-8821518\"\nheadline = \"Quality-focused value-added workforce\"\nauthor = \"Summer Hughes\"\npublished = \"2026-01-01T20:44:41.599074\"\nsection = \"Business\"\ncontent = \"Forward technology ten now spend may country ground. Upon plan generation behind our. Size development indicate operation claim road.\"\ntags = [ \"same\", \"attention\", \"former\",]\nviews = 11138\nshares = 1757\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 169
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Produce a XML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in XML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<experiment_result>\n<title>Effect of because on hand</title>\n<results>\n<metric>efficacy</metric>\n<baseline>99.92</baseline>\n<endpoint>31.19</endpoint>\n<p_value>0.3637</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>79.88</baseline>\n<endpoint>40.14</endpoint>\n<p_value>0.4331</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>57.72</baseline>\n<endpoint>41.74</endpoint>\n<p_value>0.1666</p_value>\n</results>\n<results>\n<metric>safety</metric>\n<baseline>47.88</baseline>\n<endpoint>85.33</endpoint>\n<p_value>0.3608</p_value>\n</results>\n<methodology>\n<design>RCT</design>\n<sample_size>765</sample_size>\n<duration_days>241</duration_days>\n</methodology>\n</experiment_result>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 263
} |
[
{
"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:\ncourse_id: CRS-5796\ncode: BSI420\ntitle: Expanded needs-based hub 101\ninstructor: Sarah Collins\ncredits: 3\nterm: Fall 2022\nschedule:\n- week: 1\n topic: number\n- week: 2\n topic: single\n- week: 3\n topic: personal\n- week: 4\n topic: our\n- week: 5\n topic: consumer\n- week: 6\n topic: trouble\n- week: 7\n topic: tree\n- week: 8\n topic: firm\n- week: 9\n topic: range\n- week: 10\n topic: over\n- week: 11\n topic: want\ngrading:\n homework: 30\n midterm: 30\n final: 40\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from YAML to JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"course_id\": \"CRS-5796\",\n \"code\": \"BSI420\",\n \"title\": \"Expanded needs-based hub 101\",\n \"instructor\": \"Sarah Collins\",\n \"credits\": 3,\n \"term\": \"Fall 2022\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"number\"\n },\n {\n \"week\": 2,\n \"topic\": \"single\"\n },\n {\n \"week\": 3,\n \"topic\": \"personal\"\n },\n {\n \"week\": 4,\n \"topic\": \"our\"\n },\n {\n \"week\": 5,\n \"topic\": \"consumer\"\n },\n {\n \"week\": 6,\n \"topic\": \"trouble\"\n },\n {\n \"week\": 7,\n \"topic\": \"tree\"\n },\n {\n \"week\": 8,\n \"topic\": \"firm\"\n },\n {\n \"week\": 9,\n \"topic\": \"range\"\n },\n {\n \"week\": 10,\n \"topic\": \"over\"\n },\n {\n \"week\": 11,\n \"topic\": \"want\"\n }\n ],\n \"grading\": {\n \"homework\": 30,\n \"midterm\": 30,\n \"final\": 40\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 291
} |
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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<transaction_record>\n<txn_id>TXN-86465796</txn_id>\n<customer_id>8f239cfc-bdbc-4a82-9121-b588096e290b</customer_id>\n<timestamp>2026-01-07T01:26:12.345353</timestamp>\n<items>\n<sku>SKU-78354</sku>\n<qty>1</qty>\n<price>289.73</price>\n</items>\n<items>\n<sku>SKU-13609</sku>\n<qty>1</qty>\n<price>322.15</price>\n</items>\n<items>\n<sku>SKU-34282</sku>\n<qty>5</qty>\n<price>483.05</price>\n</items>\n<subtotal>706.99</subtotal>\n<tax>109.65</tax>\n<total>529.31</total>\n<payment_method>apple_pay</payment_method>\n</transaction_record>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 217
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output student assessment as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment in TOML\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ngrade = \"B\"\ntype = \"assignment\"\nstudent_id = \"STU-866146\"\ndate = \"2026-01-05\"\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 95
} |
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\narticle_id = \"ART-1929345\"\nheadline = \"Operative exuding process improvement\"\nauthor = \"Jonathan Bray\"\npublished = \"2026-01-04T11:58:45.141825\"\nsection = \"Politics\"\ncontent = \"Us happen beautiful modern arm hope. Best southern let out use and thus approach.\\nCourt pass run degree. Party ten goal dream hear dark activity.\\nReally fly brother when together training bag. Significant major skill after family style.\"\ntags = [ \"thought\", \"education\", \"no\", \"particularly\",]\nviews = 80295\nshares = 1283\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 199
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<social_media_post>\n<username>jaclyn09</username>\n<user_id>1e991d1f-4319-48f9-9bc2-b7c30fbe8bfe</user_id>\n<hashtags>#significant</hashtags>\n<hashtags>#case</hashtags>\n<engagement>\n<likes>7546</likes>\n<shares>487</shares>\n<comments>80</comments>\n</engagement>\n<timestamp>2026-01-07T01:26:11.795990</timestamp>\n</social_media_post>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from XML to 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. Transform values to match the target format specifications.\n\nOutput:\nusername: jaclyn09\nuser_id: 1e991d1f-4319-48f9-9bc2-b7c30fbe8bfe\nhashtags:\n- '#significant'\n- '#case'\nengagement:\n likes: 7546\n shares: 487\n comments: 80\ntimestamp: '2026-01-07T01:26:11.795990'\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 130
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output research paper as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\nWe realize sing laugh room wish boy. Look physical movement prevent stuff very real draw.,\"[{\"\"name\"\": \"\"Timothy Bass\"\", \"\"affiliation\"\": \"\"Clark-Fisher\"\", \"\"email\"\": \"\"jamie52@example.net\"\"}, {\"\"name\"\": \"\"\",288,Diaz-Smith,\"[\"\"family\"\", \"\"develop\"\", \"\"strong\"\"]\",arXiv:2021.87440,10.5535/teRG,Cell,2021,Re-contextualized discrete interface\r\nEnough work firm develop course change. Order method add resource better.,\"[{\"\"name\"\": \"\"Roger Cruz\"\", \"\"affiliation\"\": \"\"Cruz PLC\"\", \"\"email\"\": \"\"jasonrich@example.org\"\"}, {\"\"name\"\": \"\"Kiar\",178,Bush LLC,\"[\"\"factor\"\", \"\"out\"\", \"\"campaign\"\"]\",arXiv:2022.95903,10.8673/KgxI,Nature,2024,Triple-buffered fresh-thinking Local Area Network\r\nWould probably small keep. Around itself develop say probably easy that. View lay within always part,\"[{\"\"name\"\": \"\"Brian Robinson\"\", \"\"affiliation\"\": \"\"Mclaughlin, Davis and Woods\"\", \"\"email\"\": \"\"jonesrichard@exa\",383,None,\"[\"\"religious\"\", \"\"attack\"\", \"\"nice\"\", \"\"wall\"\"]\",arXiv:2024.90599,10.7969/RbKT,Science,2020,Business-focused well-modulated circuit\r\nIssue upon base late trade international drug. Bank out us section indicate cover.,\"[{\"\"name\"\": \"\"Aaron Silva\"\", \"\"affiliation\"\": \"\"Hernandez and Sons\"\", \"\"email\"\": \"\"ricepatricia@example.net\"\"}, \",290,None,\"[\"\"stop\"\", \"\"difference\"\", \"\"structure\"\"]\",arXiv:2022.15085,10.5801/sPXu,Science,2020,Decentralized zero tolerance middleware\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 448
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate news article data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article in XML\n2. Complexity: 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<news_article>\n<article_id>ART-8571310</article_id>\n<headline>Inverse mission-critical customer loyalty</headline>\n<author>Patrick Evans</author>\n<published>2026-01-05T23:29:15.376210</published>\n<section>Tech</section>\n<content>Media happen whether southern sister step majority. Her ability good next fall. Business remain than fast.\nFine western gun air. But stock successful really member responsibility. I art wrong national. Son can watch apply collection you.\nAfter list face raise. Such determine describe customer.</content>\n<tags>series</tags>\n<tags>general</tags>\n<tags>size</tags>\n<tags>hour</tags>\n<tags>high</tags>\n<views>59467</views>\n<shares>3016</shares>\n</news_article>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 258
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in CSV\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nSWF476,CRS-1775,4,40,30,30,Erik Walters,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"would\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"whatever\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"support\"\"}, {\",Fall 2023,Down-sized executive Graphical User Interface 101\r\nBCB355,CRS-5908,4,40,30,30,Marcus Lewis,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"wind\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"chance\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"easy\"\"}, {\"\"week\"\"\",Spring 2020,Customizable regional toolset 101\r\nMYX299,CRS-4408,3,40,30,30,Sara Freeman,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"policy\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"agent\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"up\"\"}, {\"\"week\"\":\",Spring 2023,Organized even-keeled throughput 101\r\nJXX119,CRS-4727,3,40,30,30,Kevin Sharp,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"method\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"TV\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"stuff\"\"}, {\"\"week\"\":\",Fall 2022,Stand-alone empowering policy 101\r\n"
}
] | {
"format": "csv",
"complexity": "medium",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 315
} |
[
{
"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-1418123</note_id>\n<patient>\n<mrn>MRN-447779</mrn>\n<age>70</age>\n<gender>F</gender>\n</patient>\n<encounter_date>2026-01-03</encounter_date>\n<chief_complaint>chest pain</chief_complaint>\n<vitals>\n<bp>123/61</bp>\n<hr>81</hr>\n<temp_f>97.7</temp_f>\n</vitals>\n<assessment>\n<problem>diabetes</problem>\n<icd10>K28</icd10>\n</assessment>\n<assessment>\n<problem>hypertension</problem>\n<icd10>I98</icd10>\n</assessment>\n<assessment>\n<problem>diabetes</problem>\n<icd10>K37</icd10>\n</assessment>\n</clinical_note>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 217
} |
[
{
"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 news article."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create news article 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 \"article_id\": \"ART-3458023\",\n \"headline\": \"Future-proofed systemic matrix\",\n \"author\": \"John Richardson\",\n \"published\": \"2026-01-01T02:41:45.411141\",\n \"section\": \"Sports\",\n \"content\": \"Century hot boy money available. Article plant threat sit explain. Represent quality value dream company television.\\nBut word dinner recent. Security education responsibility nor standard decision.\",\n \"tags\": [\n \"my\",\n \"piece\",\n \"operation\"\n ],\n \"views\": 28967,\n \"shares\": 3561\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "news_article",
"type": "generation",
"estimated_tokens": 198
} |
[
{
"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: 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:\nrating = 4\nverified_purchase = true\ndate = \"2026-01-04\"\nreview_id = \"REV-1671808\"\n"
}
] | {
"format": "toml",
"complexity": "simple",
"schema": "customer_review",
"type": "generation",
"estimated_tokens": 96
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate api specification data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"Enterprise-wide solution-oriented circuit API\",\n \"version\": \"1.0.0\"\n },\n \"paths\": {\n \"/several\": {\n \"get\": {\n \"summary\": \"Painting space all five we exactly now.\",\n \"parameters\": [\n {\n \"name\": \"param0\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param1\",\n \"in\": \"query\",\n \"type\": \"string\"\n },\n {\n \"name\": \"param2\",\n \"in\": \"query\",\n \"type\": \"string\"\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"400\": {\n \"description\": \"Bad Request\"\n }\n }\n }\n }\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 277
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate social media post data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create social media post 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<social_media_post>\n<post_id>POST-23229146</post_id>\n<platform>facebook</platform>\n<user_id>0f7b6e10-e65d-4c0f-84f8-a0e4bdfc3ce6</user_id>\n<username>tapiacheryl</username>\n<content>Happy it environmental measure building drive. Major reduce night leave sea industry energy. Assume boy let.</content>\n<timestamp>2026-01-07T01:26:11.952466</timestamp>\n<hashtags>#evidence</hashtags>\n<hashtags>#ready</hashtags>\n<hashtags>#leader</hashtags>\n<engagement>\n<likes>8987</likes>\n<shares>325</shares>\n<comments>314</comments>\n</engagement>\n</social_media_post>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "social_media_post",
"type": "generation",
"estimated_tokens": 225
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this YAML data into JSON format:\nerror_id: 7ebb1ca8-2b77-4e26-9c11-c5014ddcb454\ntimestamp: '2026-01-07T01:26:11.976077'\nlevel: CRITICAL\nservice: kindService\nmessage: Grow great down almost short.\nstack_trace:\n- at political.py:437\n- at follow.py:365\n- at result.py:113\ncontext:\n user_id: 5e02da82-d5c2-4d20-b42d-a78fe30128cf\n request_id: bf1d128f-5872-4397-9a46-f624a4d8e0c0\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert error log 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 \"error_id\": \"7ebb1ca8-2b77-4e26-9c11-c5014ddcb454\",\n \"timestamp\": \"2026-01-07T01:26:11.976077\",\n \"level\": \"CRITICAL\",\n \"service\": \"kindService\",\n \"message\": \"Grow great down almost short.\",\n \"stack_trace\": [\n \"at political.py:437\",\n \"at follow.py:365\",\n \"at result.py:113\"\n ],\n \"context\": {\n \"user_id\": \"5e02da82-d5c2-4d20-b42d-a78fe30128cf\",\n \"request_id\": \"bf1d128f-5872-4397-9a46-f624a4d8e0c0\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "conversion",
"estimated_tokens": 185
} |
[
{
"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 \"value\": 97981,\n \"status\": \"pending\",\n \"effective_date\": \"2026-01-01\",\n \"parties\": [\n {\n \"name\": \"Merritt, Singh and Fitzgerald\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Weaver PLC\",\n \"role\": \"party_b\"\n }\n ],\n \"term_months\": 39\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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<contract>\n<value>97981</value>\n<status>pending</status>\n<effective_date>2026-01-01</effective_date>\n<parties>\n<name>Merritt, Singh and Fitzgerald</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Weaver PLC</name>\n<role>party_b</role>\n</parties>\n<term_months>39</term_months>\n</contract>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 161
} |
[
{
"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-8591</course_id>\n<code>DJJ155</code>\n<title>Sharable maximized product 101</title>\n<instructor>Shannon Freeman</instructor>\n<credits>4</credits>\n<term>Spring 2022</term>\n<schedule>\n<week>1</week>\n<topic>seek</topic>\n</schedule>\n<schedule>\n<week>2</week>\n<topic>board</topic>\n</schedule>\n<schedule>\n<week>3</week>\n<topic>age</topic>\n</schedule>\n<schedule>\n<week>4</week>\n<topic>usually</topic>\n</schedule>\n<schedule>\n<week>5</week>\n<topic>reason</topic>\n</schedule>\n<schedule>\n<week>6</week>\n<topic>respond</topic>\n</schedule>\n<schedule>\n<week>7</week>\n<topic>focus</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-8591\",\n \"code\": \"DJJ155\",\n \"title\": \"Sharable maximized product 101\",\n \"instructor\": \"Shannon Freeman\",\n \"credits\": 4,\n \"term\": \"Spring 2022\",\n \"schedule\": [\n {\n \"week\": 1,\n \"topic\": \"seek\"\n },\n {\n \"week\": 2,\n \"topic\": \"board\"\n },\n {\n \"week\": 3,\n \"topic\": \"age\"\n },\n {\n \"week\": 4,\n \"topic\": \"usually\"\n },\n {\n \"week\": 5,\n \"topic\": \"reason\"\n },\n {\n \"week\": 6,\n \"topic\": \"respond\"\n },\n {\n \"week\": 7,\n \"topic\": \"focus\"\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": 239
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\nabstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold\r\n,,\"[{\"\"name\"\": \"\"online\"\", \"\"revenue\"\": 2281841, \"\"growth\"\": 12.7}, {\"\"name\"\": \"\"retail\"\", \"\"revenue\"\": 1714859, \"\"gro\",,,,,January 2022,,,,,\"[{\"\"sku\"\": \"\"SKU-2323\"\", \"\"sales\"\": 285676}, {\"\"sku\"\": \"\"SKU-2670\"\", \"\"sales\"\": 378071}, {\"\"sku\"\": \"\"SKU-6091\"\", \"\"sa\",5531867,51554\r\nFire better structure economy agree interesting. Eat serve two ball meet whole finish. Industry brot,\"[{\"\"name\"\": \"\"Jillian Davis\"\", \"\"affiliation\"\": \"\"Holloway-Carrillo\"\", \"\"email\"\": \"\"david33@example.net\"\"}, {\"\"na\",,103,None,\"[\"\"happy\"\", \"\"impact\"\", \"\"cup\"\", \"\"represent\"\", \"\"today\"\"]\",arXiv:2024.90776,,10.4610/Hfcb,Science,2024,Balanced systematic attitude,,,\r\nCivil else kind development. Later responsibility page rich wrong leader.,\"[{\"\"name\"\": \"\"Derek Hicks\"\", \"\"affiliation\"\": \"\"Shaw-Sanchez\"\", \"\"email\"\": \"\"landryjason@example.com\"\"}, {\"\"name\"\"\",,500,None,\"[\"\"sense\"\", \"\"expect\"\", \"\"quickly\"\", \"\"outside\"\"]\",arXiv:2023.69799,,10.7675/QIQj,Science,2022,Customizable explicit methodology,,,\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert sales analytics from CSV to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"period\": \"January 2022\",\n \"total_revenue\": 5531867,\n \"units_sold\": 51554,\n \"channels\": [\n {\n \"name\": \"online\",\n \"revenue\": 2281841,\n \"growth\": 12.7\n },\n {\n \"name\": \"retail\",\n \"revenue\": 1714859,\n \"growth\": 33.17\n }\n ],\n \"top_products\": [\n {\n \"sku\": \"SKU-2323\",\n \"sales\": 285676\n },\n {\n \"sku\": \"SKU-2670\",\n \"sales\": 378071\n },\n {\n \"sku\": \"SKU-6091\",\n \"sales\": 425037\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "sales_analytics",
"type": "conversion",
"estimated_tokens": 198
} |
[
{
"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 contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract 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<contract>\n<contract_id>CTR-594897</contract_id>\n<parties>\n<name>Nguyen-Reeves</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Williams-Andrade</name>\n<role>party_b</role>\n</parties>\n<effective_date>2026-01-04</effective_date>\n<term_months>16</term_months>\n<value>736511</value>\n<status>executed</status>\n</contract>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 166
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Output clinical note as TOML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note 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:\nnote_id = \"CN-6667298\"\nencounter_date = \"2026-01-03\"\nchief_complaint = \"chest pain\"\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"I15\"\n\n[[assessment]]\nproblem = \"diabetes\"\nicd10 = \"I61\"\n\n[patient]\nmrn = \"MRN-706439\"\nage = 41\ngender = \"M\"\n\n[vitals]\nbp = \"113/102\"\nhr = 109\ntemp_f = 101.6\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 145
} |
[
{
"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: 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-5906907\",\n \"patient_mrn\": \"MRN-752729\",\n \"order_date\": \"2026-01-01\",\n \"panel\": \"CMP\",\n \"results\": [\n {\n \"test\": \"WBC\",\n \"value\": 184.8,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 124.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 109.9,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 67.3,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 175.8,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 235
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Convert the following CSV to JSON:\norder_date,panel,patient_mrn,result_id,results\r\n2026-01-01,CBC,MRN-506756,LAB-6952132,\"[{\"\"test\"\": \"\"Glucose\"\", \"\"value\"\": 50.5, \"\"unit\"\": \"\"mg/dL\"\", \"\"flag\"\": \"\"high\"\"}, {\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 54.6,\"\r\n2026-01-02,CBC,MRN-878861,LAB-5260724,\"[{\"\"test\"\": \"\"Glucose\"\", \"\"value\"\": 84.5, \"\"unit\"\": \"\"mg/dL\"\", \"\"flag\"\": \"\"low\"\"}, {\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 90.8, \"\r\n2026-01-01,CBC,MRN-962981,LAB-1177493,\"[{\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 174.5, \"\"unit\"\": \"\"g/dL\"\", \"\"flag\"\": \"\"high\"\"}, {\"\"test\"\": \"\"WBC\"\", \"\"value\"\": 70.3, \"\"un\"\r\n2026-01-06,CBC,MRN-465581,LAB-3148915,\"[{\"\"test\"\": \"\"Hemoglobin\"\", \"\"value\"\": 138.9, \"\"unit\"\": \"\"g/dL\"\", \"\"flag\"\": \"\"high\"\"}, {\"\"test\"\": \"\"Hemoglobin\"\", \"\"val\"\r\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result from CSV to JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\n{\n \"result_id\": \"LAB-6952132\",\n \"patient_mrn\": \"MRN-506756\",\n \"order_date\": \"2026-01-01\",\n \"panel\": \"CBC\",\n \"results\": [\n {\n \"test\": \"Glucose\",\n \"value\": 50.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 54.6,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Glucose\",\n \"value\": 80.5,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 76.6,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 133.2,\n \"unit\": \"g/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 167.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "lab_result",
"type": "conversion",
"estimated_tokens": 260
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output experiment result as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\nsignificant,EXP-122198,RCT,212,67,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 74.69, \"\"endpoint\"\": 66.28, \"\"p_value\"\": 0.1604}, {\"\"metric\"\": \"\"safety\"\",\",Effect of my on want\r\nsignificant,EXP-708552,observational,218,817,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 62.23, \"\"endpoint\"\": 99.83, \"\"p_value\"\": 0.4128}, {\"\"metric\"\": \"\"efficacy\",Effect of material on government\r\nsignificant,EXP-210080,cohort,213,939,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 38.39, \"\"endpoint\"\": 24.01, \"\"p_value\"\": 0.3116}, {\"\"metric\"\": \"\"safety\"\",\",Effect of before on want\r\nnon-significant,EXP-349503,observational,131,573,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 81.07, \"\"endpoint\"\": 81.27, \"\"p_value\"\": 0.2522}, {\"\"metric\"\": \"\"safety\",Effect of size on human\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 290
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Reformat the data below from YAML to JSON:\nproduct_id: PROD-183642\nname: User-friendly reciprocal knowledge user\ncategory: electronics\nprice: 773.65\ncurrency: USD\nstock: 982\nis_available: true\nrating: 4.12\nreviews: 487\nspecs:\n weight_kg: 15.73\n dimensions: 53x68x64cm\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert product listing from YAML 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 \"product_id\": \"PROD-183642\",\n \"name\": \"User-friendly reciprocal knowledge user\",\n \"category\": \"electronics\",\n \"price\": 773.65,\n \"currency\": \"USD\",\n \"stock\": 982,\n \"is_available\": true,\n \"rating\": 4.12,\n \"reviews\": 487,\n \"specs\": {\n \"weight_kg\": 15.73,\n \"dimensions\": \"53x68x64cm\"\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "product_listing",
"type": "conversion",
"estimated_tokens": 155
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J30\"\"}]\",headache,2026-01-05,CN-5728788,18,F,MRN-724840,92/79,75,97.9\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I88\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K14\"\"}, {\"\"problem\"\": \"\"\",fever,2026-01-06,CN-5844535,52,M,MRN-434147,147/65,115,99.6\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J67\"\"}, {\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"I31\"\"}, {\"\"problem\"\": \"\"diab\",fever,2026-01-01,CN-7583869,48,F,MRN-720491,144/70,75,97.3\r\n\"[{\"\"problem\"\": \"\"diabetes\"\", \"\"icd10\"\": \"\"J78\"\"}, {\"\"problem\"\": \"\"hypertension\"\", \"\"icd10\"\": \"\"K18\"\"}, {\"\"problem\"\": \"\"\",chest pain,2026-01-05,CN-1908881,50,M,MRN-476655,140/72,120,101.4\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 275
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Produce a YAML document for a contract."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create contract in YAML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncontract_id: CTR-570925\nparties:\n- name: Herring, Wolf and White\n role: party_a\n- name: Rodriguez, Lawrence and Smith\n role: party_b\neffective_date: '2026-01-05'\nterm_months: 50\nvalue: 698924\nstatus: executed\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "contract",
"type": "generation",
"estimated_tokens": 128
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Output product listing as XML."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in XML\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: well-formed tags, proper nesting, escaped special chars\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<product_listing>\n<product_id>PROD-626408</product_id>\n<name>Business-focused next generation array</name>\n<category>clothing</category>\n<price>526.29</price>\n<currency>USD</currency>\n<stock>20</stock>\n<is_available>True</is_available>\n<rating>4.14</rating>\n<reviews>578</reviews>\n<specs>\n<weight_kg>48.12</weight_kg>\n<dimensions>30x61x73cm</dimensions>\n</specs>\n</product_listing>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 182
} |
[
{
"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 api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nopenapi = \"3.0.0\"\n\n[info]\ntitle = \"Mandatory zero administration Internet solution API\"\nversion = \"1.0.0\"\n\n[paths.\"/conference\".get]\nsummary = \"Significant security have good wind director.\"\n[[paths.\"/conference\".get.parameters]]\nname = \"param0\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/conference\".get.parameters]]\nname = \"param1\"\nin = \"query\"\ntype = \"string\"\n\n[[paths.\"/conference\".get.parameters]]\nname = \"param2\"\nin = \"query\"\ntype = \"string\"\n\n[paths.\"/conference\".get.responses.200]\ndescription = \"Success\"\n\n[paths.\"/conference\".get.responses.400]\ndescription = \"Bad Request\"\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 220
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this JSON data into YAML format:\n{\n \"experiment_id\": \"EXP-826350\",\n \"title\": \"Effect of decision on who\",\n \"methodology\": {\n \"design\": \"RCT\",\n \"sample_size\": 605,\n \"duration_days\": 103\n },\n \"results\": [\n {\n \"metric\": \"efficacy\",\n \"baseline\": 56.04,\n \"endpoint\": 39.98,\n \"p_value\": 0.2349\n },\n {\n \"metric\": \"safety\",\n \"baseline\": 79.65,\n \"endpoint\": 52.3,\n \"p_value\": 0.0188\n }\n ],\n \"conclusion\": \"non-significant\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert experiment result from JSON to YAML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: consistent indentation, colon-space syntax, hyphen lists\n4. Structure: Organize data logically with appropriate nesting\n5. Transform values to match the target format specifications.\n\nOutput:\nexperiment_id: EXP-826350\ntitle: Effect of decision on who\nmethodology:\n design: RCT\n sample_size: 605\n duration_days: 103\nresults:\n- metric: efficacy\n baseline: 56.04\n endpoint: 39.98\n p_value: 0.2349\n- metric: safety\n baseline: 79.65\n endpoint: 52.3\n p_value: 0.0188\nconclusion: non-significant\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "experiment_result",
"type": "conversion",
"estimated_tokens": 156
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Reformat the data below from XML to YAML:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<social_media_post>\n<hashtags>#economic</hashtags>\n<hashtags>#director</hashtags>\n<hashtags>#this</hashtags>\n<hashtags>#baby</hashtags>\n<username>sparkshaley</username>\n<engagement>\n<likes>5699</likes>\n<shares>534</shares>\n<comments>185</comments>\n</engagement>\n<platform>instagram</platform>\n<content>Garden note than theory language. Fine behind office lead pick. Identify simply nation partner machine health. Wind recently since set whom standard.</content>\n</social_media_post>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert social media post from XML to 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. Transform values to match the target format specifications.\n\nOutput:\nhashtags:\n- '#economic'\n- '#director'\n- '#this'\n- '#baby'\nusername: sparkshaley\nengagement:\n likes: 5699\n shares: 534\n comments: 185\nplatform: instagram\ncontent: Garden note than theory language. Fine behind office lead pick. Identify\n simply nation partner machine health. Wind recently since set whom standard.\n"
}
] | {
"format": "yaml",
"complexity": "simple",
"schema": "social_media_post",
"type": "conversion",
"estimated_tokens": 160
} |
[
{
"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 transaction record."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create transaction record 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:\ntxn_id: TXN-56334956\ncustomer_id: 22233344-f0f2-434c-869c-d919b13dbc85\ntimestamp: '2026-01-07T01:26:11.318292'\nitems:\n- sku: SKU-28497\n qty: 5\n price: 124.08\n- sku: SKU-64150\n qty: 4\n price: 49.31\n- sku: SKU-68367\n qty: 3\n price: 96.12\nsubtotal: 767.52\ntax: 44.4\ntotal: 112.37\npayment_method: credit_card\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "transaction_record",
"type": "generation",
"estimated_tokens": 156
} |
[
{
"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-624647\",\n \"effective_date\": \"2026-01-03\",\n \"term_months\": 13,\n \"status\": \"pending\",\n \"parties\": [\n {\n \"name\": \"Graves-George\",\n \"role\": \"party_a\"\n },\n {\n \"name\": \"Bradley-Beltran\",\n \"role\": \"party_b\"\n }\n ]\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert contract 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<contract>\n<contract_id>CTR-624647</contract_id>\n<effective_date>2026-01-03</effective_date>\n<term_months>13</term_months>\n<status>pending</status>\n<parties>\n<name>Graves-George</name>\n<role>party_a</role>\n</parties>\n<parties>\n<name>Bradley-Beltran</name>\n<role>party_b</role>\n</parties>\n</contract>"
}
] | {
"format": "xml",
"complexity": "simple",
"schema": "contract",
"type": "conversion",
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Transform this YAML data into JSON format:\ncredits: 4\ncourse_id: CRS-8616\ninstructor: Amy Rivera\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert course syllabus from YAML 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 \"credits\": 4,\n \"course_id\": \"CRS-8616\",\n \"instructor\": \"Amy Rivera\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "course_syllabus",
"type": "conversion",
"estimated_tokens": 99
} |
[
{
"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 prescription."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create prescription in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nrx_id = \"RX-9666876\"\npatient_mrn = \"MRN-499732\"\nprescriber = \"Stacy Allen\"\ndate = \"2026-01-03\"\n[[medications]]\nname = \"Lisinopril\"\ndosage = \"10mg\"\nfrequency = \"TID\"\nquantity = 60\n\n[[medications]]\nname = \"Metformin\"\ndosage = \"10mg\"\nfrequency = \"BID\"\nquantity = 60\n\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "prescription",
"type": "generation",
"estimated_tokens": 140
} |
[
{
"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 financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report 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<financial_report>\n<company>Casey-Hale</company>\n<ticker>HOJO</ticker>\n<quarter>Q2 2022</quarter>\n<revenue>10616979</revenue>\n<expenses>49970613</expenses>\n<net_income>4124896</net_income>\n<eps>5.18</eps>\n<metrics>\n<profit_margin>25.75</profit_margin>\n<roe>5.45</roe>\n</metrics>\n</financial_report>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 162
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Generate experiment result data in CSV format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in CSV\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nconclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title\r\nsignificant,EXP-235027,,,,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 65.08, \"\"endpoint\"\": 79.76, \"\"p_value\"\": 0.2187}, {\"\"metric\"\": \"\"safety\"\",\",Effect of personal on mouth\r\nnon-significant,EXP-140923,RCT,182,404,\"[{\"\"metric\"\": \"\"efficacy\"\", \"\"baseline\"\": 50.74, \"\"endpoint\"\": 82.93, \"\"p_value\"\": 0.098}, {\"\"metric\"\": \"\"safety\"\"\",Effect of morning on price\r\nsignificant,EXP-102509,RCT,161,660,\"[{\"\"metric\"\": \"\"safety\"\", \"\"baseline\"\": 82.05, \"\"endpoint\"\": 92.5, \"\"p_value\"\": 0.1171}, {\"\"metric\"\": \"\"efficacy\"\"\",Effect of line on always\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 239
} |
[
{
"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: medium - 5-8 fields, 2-3 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nassessment_id = \"ASMT-828472\"\nstudent_id = \"STU-735131\"\ncourse_id = \"CRS-8725\"\ntype = \"quiz\"\ndate = \"2026-01-04\"\ntotal_score = 67\npercentage = 50.34\ngrade = \"A\"\n[[scores]]\nquestion = 1\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 2\npoints_earned = 10\npoints_possible = 10\n\n[[scores]]\nquestion = 3\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 4\npoints_earned = 6\npoints_possible = 10\n\n[[scores]]\nquestion = 5\npoints_earned = 9\npoints_possible = 10\n\n[[scores]]\nquestion = 6\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 7\npoints_earned = 0\npoints_possible = 10\n\n[[scores]]\nquestion = 8\npoints_earned = 4\npoints_possible = 10\n\n[[scores]]\nquestion = 9\npoints_earned = 5\npoints_possible = 10\n\n[[scores]]\nquestion = 10\npoints_earned = 7\npoints_possible = 10\n\n[[scores]]\nquestion = 11\npoints_earned = 2\npoints_possible = 10\n\n[[scores]]\nquestion = 12\npoints_earned = 0\npoints_possible = 10\n\n"
}
] | {
"format": "toml",
"complexity": "medium",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 308
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a api specification."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create api specification in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/total_get_parameters,paths_/total_get_responses_200_description,paths_/total_get_responses_400_description,paths_/total_get_summary,publication_doi,publication_venue,publication_year,title\r\n,,,,Business-focused composite flexibility API,1.0.0,,3.0.0,,\"[{\"\"name\"\": \"\"param0\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"string\"\"}, {\"\"name\"\": \"\"param1\"\", \"\"in\"\": \"\"query\"\", \"\"type\"\": \"\"str\",Success,Bad Request,Building public truth decade.,,,,\r\nChoice condition girl become lawyer yourself player. Mrs mean decide scene never. Fear society in wa,\"[{\"\"name\"\": \"\"Dr. Stephanie Boyer\"\", \"\"affiliation\"\": \"\"Davis-Novak\"\", \"\"email\"\": \"\"lowerydavid@example.com\"\"}, \",381,None,,,\"[\"\"garden\"\", \"\"entire\"\", \"\"hold\"\", \"\"doctor\"\"]\",,arXiv:2020.18018,,,,,10.8624/QDSU,Nature,2021,Compatible reciprocal projection\r\n\"She begin process treatment him ball quickly. Market according foreign half simply yet end offer.\nNa\",\"[{\"\"name\"\": \"\"Bob Blair\"\", \"\"affiliation\"\": \"\"Mccormick Ltd\"\", \"\"email\"\": \"\"miguellee@example.org\"\"}, {\"\"name\"\": \"\"\",214,\"Wood, Oliver and Bradley\",,,\"[\"\"they\"\", \"\"word\"\", \"\"fact\"\", \"\"nature\"\"]\",,arXiv:2021.61642,,,,,10.9862/zsAH,Cell,2023,Operative leadingedge knowledge user\r\nPrice today watch business smile have. Most head strategy carry something.,\"[{\"\"name\"\": \"\"Douglas Diaz\"\", \"\"affiliation\"\": \"\"Olsen, Miller and Patel\"\", \"\"email\"\": \"\"bruce62@example.org\"\"},\",136,Snyder and Sons,,,\"[\"\"natural\"\", \"\"require\"\", \"\"lot\"\"]\",,arXiv:2020.61870,,,,,10.7952/XkSf,Science,2020,Organized user-facing success\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "api_specification",
"type": "generation",
"estimated_tokens": 477
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of financial report."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create financial report in JSON\n2. Complexity: medium - 5-8 fields, 2-3 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"company\": \"Foster, Villegas and Allen\",\n \"ticker\": \"IDEC\",\n \"quarter\": \"Q4 2020\",\n \"revenue\": 77017744,\n \"expenses\": 3181180,\n \"net_income\": 10938761,\n \"eps\": 6.78,\n \"metrics\": {\n \"profit_margin\": 10.92,\n \"roe\": 12.41\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "generation",
"estimated_tokens": 138
} |
[
{
"role": "system",
"content": "You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML."
},
{
"role": "user",
"content": "Transform this XML data into YAML format:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<lab_result>\n<result_id>LAB-6261333</result_id>\n<patient_mrn>MRN-419465</patient_mrn>\n<order_date>2026-01-06</order_date>\n<panel>CMP</panel>\n<results>\n<test>Glucose</test>\n<value>185.8</value>\n<unit>mg/dL</unit>\n<flag>low</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>185.4</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>150.2</value>\n<unit>g/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>61.0</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>81.5</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n<results>\n<test>Hemoglobin</test>\n<value>69.1</value>\n<unit>mg/dL</unit>\n<flag>normal</flag>\n</results>\n<results>\n<test>WBC</test>\n<value>155.0</value>\n<unit>g/dL</unit>\n<flag>high</flag>\n</results>\n</lab_result>"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert lab result 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:\nresult_id: LAB-6261333\npatient_mrn: MRN-419465\norder_date: '2026-01-06'\npanel: CMP\nresults:\n- test: Glucose\n value: 185.8\n unit: mg/dL\n flag: low\n- test: Hemoglobin\n value: 185.4\n unit: mg/dL\n flag: normal\n- test: WBC\n value: 150.2\n unit: g/dL\n flag: normal\n- test: WBC\n value: 61.0\n unit: g/dL\n flag: high\n- test: Hemoglobin\n value: 81.5\n unit: g/dL\n flag: high\n- test: Hemoglobin\n value: 69.1\n unit: mg/dL\n flag: normal\n- test: WBC\n value: 155.0\n unit: g/dL\n flag: high\n"
}
] | {
"format": "yaml",
"complexity": "medium",
"schema": "lab_result",
"type": "conversion",
"estimated_tokens": 201
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Create a JSON representation of lab result."
},
{
"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-6261333\",\n \"patient_mrn\": \"MRN-419465\",\n \"order_date\": \"2026-01-06\",\n \"panel\": \"CMP\",\n \"results\": [\n {\n \"test\": \"Glucose\",\n \"value\": 185.8,\n \"unit\": \"mg/dL\",\n \"flag\": \"low\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 185.4,\n \"unit\": \"mg/dL\",\n \"flag\": \"normal\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 150.2,\n \"unit\": \"g/dL\",\n \"flag\": \"normal\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 61.0,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 81.5,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n },\n {\n \"test\": \"Hemoglobin\",\n \"value\": 69.1,\n \"unit\": \"mg/dL\",\n \"flag\": \"normal\"\n },\n {\n \"test\": \"WBC\",\n \"value\": 155.0,\n \"unit\": \"g/dL\",\n \"flag\": \"high\"\n }\n ]\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "lab_result",
"type": "generation",
"estimated_tokens": 289
} |
[
{
"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 error log."
},
{
"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: ceb4c13d-be26-428c-bb79-8b309ff0c106\ntimestamp: '2026-01-07T01:26:11.623451'\nlevel: WARNING\nservice: doService\nmessage: Form brother low why eight lot hour.\nstack_trace:\n- at human.py:441\n- at walk.py:434\n- at little.py:190\n- at back.py:472\ncontext:\n user_id: aadb1d52-7785-4e8d-9556-9bbf82ac688d\n request_id: 4036c302-f392-4626-8345-dc6abf1efc62\n"
}
] | {
"format": "yaml",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 166
} |
[
{
"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 clinical note."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create clinical note in JSON\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"patient\": {\n \"mrn\": \"MRN-739501\",\n \"age\": 71,\n \"gender\": \"M\"\n },\n \"vitals\": {\n \"bp\": \"112/102\",\n \"hr\": 113,\n \"temp_f\": 100.9\n },\n \"chief_complaint\": \"fever\"\n}"
}
] | {
"format": "json",
"complexity": "simple",
"schema": "clinical_note",
"type": "generation",
"estimated_tokens": 124
} |
[
{
"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 \"paper_id\": \"arXiv:2022.13826\",\n \"title\": \"Team-oriented human-resource secured line\",\n \"authors\": [\n {\n \"name\": \"Breanna Santiago\",\n \"affiliation\": \"Long-Murphy\",\n \"email\": \"moranjason@example.org\"\n },\n {\n \"name\": \"Monica Schneider\",\n \"affiliation\": \"Jones-Preston\",\n \"email\": \"kimberly80@example.com\"\n }\n ],\n \"abstract\": \"Network represent likely nation later financial where. Minute be never admit card determine east.\\nAfter them notice election test care it.\",\n \"keywords\": [\n \"likely\",\n \"free\",\n \"star\",\n \"whose\",\n \"cell\"\n ],\n \"publication\": {\n \"venue\": \"Cell\",\n \"year\": 2023,\n \"doi\": \"10.6086/mCSr\"\n },\n \"citations\": 483,\n \"funding_source\": \"Jackson-Mcdonald\"\n}"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert research paper 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<research_paper>\n<paper_id>arXiv:2022.13826</paper_id>\n<title>Team-oriented human-resource secured line</title>\n<authors>\n<name>Breanna Santiago</name>\n<affiliation>Long-Murphy</affiliation>\n<email>moranjason@example.org</email>\n</authors>\n<authors>\n<name>Monica Schneider</name>\n<affiliation>Jones-Preston</affiliation>\n<email>kimberly80@example.com</email>\n</authors>\n<abstract>Network represent likely nation later financial where. Minute be never admit card determine east.\nAfter them notice election test care it.</abstract>\n<keywords>likely</keywords>\n<keywords>free</keywords>\n<keywords>star</keywords>\n<keywords>whose</keywords>\n<keywords>cell</keywords>\n<publication>\n<venue>Cell</venue>\n<year>2023</year>\n<doi>10.6086/mCSr</doi>\n</publication>\n<citations>483</citations>\n<funding_source>Jackson-Mcdonald</funding_source>\n</research_paper>"
}
] | {
"format": "xml",
"complexity": "medium",
"schema": "research_paper",
"type": "conversion",
"estimated_tokens": 300
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a research paper."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create research paper in CSV\n2. Complexity: simple - 3-5 fields, minimal nesting\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\nabstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title\r\n,,,,,arXiv:2024.47313,10.3290/Fkot,Cell,2021,Optional modular intranet\r\nFinally international agency well safe pretty reach pull. Learn computer senior guess.,\"[{\"\"name\"\": \"\"Andre Owens\"\", \"\"affiliation\"\": \"\"Baker-Watkins\"\", \"\"email\"\": \"\"jessewalker@example.org\"\"}, {\"\"name\",53,None,\"[\"\"area\"\", \"\"clear\"\", \"\"wear\"\", \"\"Democrat\"\"]\",arXiv:2020.67216,10.3071/uTAs,Cell,2023,Realigned cohesive matrices\r\n\"Administration news there draw. Particularly least beautiful hand.\nTruth become often Democrat age s\",\"[{\"\"name\"\": \"\"Gregory Deleon\"\", \"\"affiliation\"\": \"\"Peterson-Armstrong\"\", \"\"email\"\": \"\"dsantos@example.org\"\"}, {\"\"\",374,Alexander-Perez,\"[\"\"data\"\", \"\"data\"\", \"\"central\"\", \"\"discover\"\"]\",arXiv:2024.31069,10.4868/OjDS,Nature,2021,Open-source impactful superstructure\r\n\"Name stand page season itself dinner someone.\nCulture believe anyone year believe.\",\"[{\"\"name\"\": \"\"Charlene Cook\"\", \"\"affiliation\"\": \"\"Clark Group\"\", \"\"email\"\": \"\"gregorywayne@example.com\"\"}, {\"\"nam\",33,None,\"[\"\"scientist\"\", \"\"civil\"\", \"\"successful\"\", \"\"young\"\", \"\"development\"\"]\",arXiv:2021.55537,10.9149/abHQ,Science,2024,Innovative scalable alliance\r\n"
}
] | {
"format": "csv",
"complexity": "simple",
"schema": "research_paper",
"type": "generation",
"estimated_tokens": 388
} |
[
{
"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 course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in TOML\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: key=value syntax, [sections], proper types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncourse_id = \"CRS-9669\"\ncode = \"GGR152\"\ntitle = \"Open-source zero tolerance implementation 101\"\ninstructor = \"David Silva\"\ncredits = 3\nterm = \"Spring 2023\"\n[[schedule]]\nweek = 1\ntopic = \"blue\"\n\n[[schedule]]\nweek = 2\ntopic = \"current\"\n\n[[schedule]]\nweek = 3\ntopic = \"government\"\n\n[[schedule]]\nweek = 4\ntopic = \"partner\"\n\n[[schedule]]\nweek = 5\ntopic = \"success\"\n\n[[schedule]]\nweek = 6\ntopic = \"consumer\"\n\n[[schedule]]\nweek = 7\ntopic = \"season\"\n\n[[schedule]]\nweek = 8\ntopic = \"team\"\n\n[[schedule]]\nweek = 9\ntopic = \"rich\"\n\n[grading]\nhomework = 30\nmidterm = 30\nfinal = 40\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 216
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Output product listing as CSV."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create product listing in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncategory,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock\r\nclothing,USD,True,Profound optimizing frame,765.91,PROD-366504,2.99,733,68x14x25cm,4.05,115\r\nclothing,USD,True,Enhanced interactive capability,13.89,PROD-376142,4.47,27,50x78x54cm,37.57,924\r\nelectronics,USD,True,Self-enabling leadingedge pricing structure,636.84,PROD-946430,2.18,504,43x72x40cm,27.46,223\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "product_listing",
"type": "generation",
"estimated_tokens": 181
} |
[
{
"role": "system",
"content": "You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML."
},
{
"role": "user",
"content": "Generate student assessment data in XML format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create student assessment 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<student_assessment>\n<assessment_id>ASMT-391811</assessment_id>\n<student_id>STU-626330</student_id>\n<course_id>CRS-7911</course_id>\n<type>quiz</type>\n<date>2026-01-02</date>\n<scores>\n<question>1</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>2</question>\n<points_earned>1</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>3</question>\n<points_earned>4</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>4</question>\n<points_earned>8</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>5</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>6</question>\n<points_earned>6</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<scores>\n<question>7</question>\n<points_earned>10</points_earned>\n<points_possible>10</points_possible>\n</scores>\n<total_score>84</total_score>\n<percentage>64.45</percentage>\n<grade>C</grade>\n</student_assessment>"
}
] | {
"format": "xml",
"complexity": "complex",
"schema": "student_assessment",
"type": "generation",
"estimated_tokens": 354
} |
[
{
"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:\ncompany: Foster, Villegas and Allen\nticker: IDEC\nquarter: Q4 2020\nrevenue: 77017744\nexpenses: 3181180\nnet_income: 10938761\neps: 6.78\nmetrics:\n profit_margin: 10.92\n roe: 12.41\n"
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Convert financial report from YAML 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 \"company\": \"Foster, Villegas and Allen\",\n \"ticker\": \"IDEC\",\n \"quarter\": \"Q4 2020\",\n \"revenue\": 77017744,\n \"expenses\": 3181180,\n \"net_income\": 10938761,\n \"eps\": 6.78,\n \"metrics\": {\n \"profit_margin\": 10.92,\n \"roe\": 12.41\n }\n}"
}
] | {
"format": "json",
"complexity": "medium",
"schema": "financial_report",
"type": "conversion",
"estimated_tokens": 139
} |
[
{
"role": "system",
"content": "You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON."
},
{
"role": "user",
"content": "Generate error log data in JSON format."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create error log in JSON\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: proper braces/brackets, quoted keys, correct value types\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\n{\n \"error_id\": \"f8b4fd9d-9949-45cc-8324-991a843ab864\",\n \"timestamp\": \"2026-01-07T01:26:12.953357\",\n \"level\": \"CRITICAL\",\n \"service\": \"payService\",\n \"message\": \"Successful kid size worker if but song.\",\n \"stack_trace\": [\n \"at push.py:14\",\n \"at picture.py:318\",\n \"at but.py:245\",\n \"at serve.py:497\"\n ],\n \"context\": {\n \"user_id\": \"b5fd4334-50ed-4374-acb2-803d9b175385\",\n \"request_id\": \"84fe64b5-4a0b-48e2-af50-06ba9f28204e\"\n }\n}"
}
] | {
"format": "json",
"complexity": "complex",
"schema": "error_log",
"type": "generation",
"estimated_tokens": 189
} |
[
{
"role": "system",
"content": "You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML."
},
{
"role": "user",
"content": "Produce a TOML document for a experiment result."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create experiment result in TOML\n2. Complexity: 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:\nexperiment_id = \"EXP-974476\"\ntitle = \"Effect of card on political\"\nconclusion = \"significant\"\n[[results]]\nmetric = \"safety\"\nbaseline = 81.86\nendpoint = 95.41\np_value = 0.4221\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 28.31\nendpoint = 51.25\np_value = 0.3164\n\n[[results]]\nmetric = \"efficacy\"\nbaseline = 74.07\nendpoint = 10.16\np_value = 0.1195\n\n[[results]]\nmetric = \"safety\"\nbaseline = 73.28\nendpoint = 70.63\np_value = 0.073\n\n[methodology]\ndesign = \"cohort\"\nsample_size = 185\nduration_days = 133\n"
}
] | {
"format": "toml",
"complexity": "complex",
"schema": "experiment_result",
"type": "generation",
"estimated_tokens": 199
} |
[
{
"role": "system",
"content": "You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV."
},
{
"role": "user",
"content": "Produce a CSV document for a course syllabus."
},
{
"role": "assistant",
"content": "Approach:\n1. Task: Create course syllabus in CSV\n2. Complexity: complex - 8-10 fields, 3-4 levels\n3. Format rules: header row, comma-separated, quoted fields with commas\n4. Structure: Organize data logically with appropriate nesting\n5. Populate fields with realistic example data based on the schema.\n\nOutput:\ncode,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title\r\nMRD384,CRS-1299,3,40,30,30,David Macias,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"laugh\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"generation\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"work\"\"}, {\"\"\",Spring 2021,Optimized impactful capability 101\r\nRAI192,CRS-1453,4,40,30,30,Stephanie Sanchez,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"risk\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"question\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"my\"\"}, {\"\"week\"\"\",Spring 2022,Switchable incremental contingency 101\r\nKMW394,CRS-7564,4,40,30,30,Elizabeth Rice,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"white\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"state\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"event\"\"}, {\"\"week\",Fall 2022,Focused asymmetric extranet 101\r\nLRR330,CRS-2405,4,40,30,30,Alex Shaw,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"thus\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"six\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"someone\"\"}, {\"\"week\"\"\",Spring 2022,Robust object-oriented intranet 101\r\nYHO448,CRS-4264,4,40,30,30,Stacy Nelson,\"[{\"\"week\"\": 1, \"\"topic\"\": \"\"teach\"\"}, {\"\"week\"\": 2, \"\"topic\"\": \"\"voice\"\"}, {\"\"week\"\": 3, \"\"topic\"\": \"\"want\"\"}, {\"\"week\"\"\",Fall 2023,Total solution-oriented conglomeration 101\r\n"
}
] | {
"format": "csv",
"complexity": "complex",
"schema": "course_syllabus",
"type": "generation",
"estimated_tokens": 368
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.