[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Generate customer review data in YAML format.

[Assistant]
Approach:
1. Task: Create customer review in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
review_id: REV-7250124
product_id: PROD-375265
user_id: 48302d32-0445-4405-afc6-604ef6300782
rating: 1
title: Very responsibility coach economy sea public you.
content: 'Chair painting shake city kind good though. Find reality water support key.

  Fly party couple production fight. Live attention anyone her traditional. I room
  blood condition research fund model.'
date: '2026-01-03'
verified_purchase: true
helpful_votes: 78


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a sales analytics.

[Assistant]
Approach:
1. Task: Create sales analytics in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
period: March 2024
total_revenue: 2433324
units_sold: 8686
channels:
- name: online
  revenue: 3952303
  growth: 2.75
- name: retail
  revenue: 3970412
  growth: 12.57
top_products:
- sku: SKU-2514
  sales: 485558
- sku: SKU-5241
  sales: 142515
- sku: SKU-4600
  sales: 420300


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Generate sales analytics data in XML format.

[Assistant]
Approach:
1. Task: Create sales analytics in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>March 2024</period>
<total_revenue>2433324</total_revenue>
<units_sold>8686</units_sold>
<channels>
<name>online</name>
<revenue>3952303</revenue>
<growth>2.75</growth>
</channels>
<channels>
<name>retail</name>
<revenue>3970412</revenue>
<growth>12.57</growth>
</channels>
<top_products>
<sku>SKU-2514</sku>
<sales>485558</sales>
</top_products>
<top_products>
<sku>SKU-5241</sku>
<sales>142515</sales>
</top_products>
<top_products>
<sku>SKU-4600</sku>
<sales>420300</sales>
</top_products>
</sales_analytics>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output research paper as XML.

[Assistant]
Approach:
1. Task: Create research paper in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2024.49729</paper_id>
<title>Optimized fault-tolerant monitoring</title>
<authors>
<name>Ashley Hubbard</name>
<affiliation>Mcdonald-White</affiliation>
<email>jenniferlong@example.net</email>
</authors>
<authors>
<name>Erica Marshall</name>
<affiliation>Calderon-Dalton</affiliation>
<email>adouglas@example.org</email>
</authors>
<authors>
<name>Mercedes Campbell</name>
<affiliation>Davis-Lynch</affiliation>
<email>yharris@example.org</email>
</authors>
<abstract>Relate make read game soldier new. Agree south attorney one century drive draw.
Reduce head tax certainly offer deal. Sister station adult seat wear.</abstract>
<keywords>gas</keywords>
<keywords>understand</keywords>
<keywords>everything</keywords>
<keywords>miss</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.3465/hMKF</doi>
</publication>
<citations>65</citations>
<funding_source>Parsons Inc</funding_source>
</research_paper>


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Reformat the data below from YAML to TOML:
post_id: POST-33796851
platform: instagram
user_id: aa32cdd3-72c6-4e38-bd5e-ff3918321d73
username: qtownsend
content: List floor whatever fly. Play represent five my. Stuff area push other begin
  team. Wind leg require represent.
timestamp: '2026-01-07T13:51:26.038556'
hashtags:
- '#study'
- '#able'
- '#week'
engagement:
  likes: 3006
  shares: 53
  comments: 61

[Assistant]
Approach:
1. Task: Convert social media post from YAML to TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
post_id = "POST-33796851"
platform = "instagram"
user_id = "aa32cdd3-72c6-4e38-bd5e-ff3918321d73"
username = "qtownsend"
content = "List floor whatever fly. Play represent five my. Stuff area push other begin team. Wind leg require represent."
timestamp = "2026-01-07T13:51:26.038556"
hashtags = [ "#study", "#able", "#week",]

[engagement]
likes = 3006
shares = 53
comments = 61


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Generate api specification data in YAML format.

[Assistant]
Approach:
1. Task: Create api specification in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
openapi: 3.0.0
info:
  title: Robust demand-driven hub API
  version: 1.0.0
paths:
  /finally:
    get:
      summary: Describe experience pick treatment up remain withi
      parameters:
      - name: param0
        in: query
        type: string
      - name: param1
        in: query
        type: string
      - name: param2
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Convert the following JSON to CSV:
{
  "error_id": "e01a43f8-d4eb-4ec7-a325-ad2b31726d0f",
  "timestamp": "2026-01-07T13:51:25.462522",
  "level": "ERROR",
  "service": "winService",
  "message": "Western energy project push building.",
  "stack_trace": [
    "at could.py:42",
    "at seem.py:198"
  ],
  "context": {
    "user_id": "7197800d-0acd-4eee-b9ab-24b5158dfa0a",
    "request_id": "00c4c00d-dc22-4013-8495-1ed2381fc937"
  }
}

[Assistant]
Approach:
1. Task: Convert error log from JSON to CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
abstract,authors,citations,context_request_id,context_user_id,error_id,funding_source,keywords,level,message,paper_id,publication_doi,publication_venue,publication_year,service,stack_trace,timestamp,title
,,,00c4c00d-dc22-4013-8495-1ed2381fc937,7197800d-0acd-4eee-b9ab-24b5158dfa0a,e01a43f8-d4eb-4ec7-a325-ad2b31726d0f,,,ERROR,Western energy project push building.,,,,,winService,"[""at could.py:42"", ""at seem.py:198""]",2026-01-07T13:51:25.462522,
Join dark field develop another. Air control simply too part off call. Morning result sea.,"[{""name"": ""Terry Austin"", ""affiliation"": ""Vasquez Group"", ""email"": ""roachkrystal@example.org""}, {""na",419,,,,None,"[""understand"", ""research"", ""word"", ""great""]",,,arXiv:2022.42029,10.4747/lall,Nature,2021,,,,Switchable optimal implementation
"Matter own four. These record its audience writer control. Thank police bill everyone indeed.
Eviden","[{""name"": ""Tammy Powell"", ""affiliation"": ""Fitzgerald-Sanders"", ""email"": ""taylorjones@example.org""}, ",248,,,,None,"[""total"", ""consider"", ""available"", ""according"", ""true""]",,,arXiv:2020.67747,10.2366/OLxo,Nature,2020,,,,Self-enabling mission-critical collaboration
"Part close then.
Approach century young send his certain similar group. Yeah detail staff cell store","[{""name"": ""Elizabeth Herman"", ""affiliation"": ""Gonzales Ltd"", ""email"": ""david11@example.com""}, {""name",435,,,,Brooks-Gray,"[""serve"", ""data"", ""position"", ""into"", ""choose""]",,,arXiv:2023.73294,10.2782/dnHH,Science,2023,,,,Pre-emptive explicit collaboration


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Produce a TOML document for a clinical note.

[Assistant]
Approach:
1. Task: Create clinical note in TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
note_id = "CN-3823498"
encounter_date = "2026-01-06"

[vitals]
bp = "131/104"
hr = 84
temp_f = 99.9


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following JSON to XML:
{
  "eps": 6.0,
  "company": "Richardson-Gonzalez",
  "quarter": "Q3 2020",
  "net_income": 13953656
}

[Assistant]
Approach:
1. Task: Convert financial report from JSON to XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<eps>6.0</eps>
<company>Richardson-Gonzalez</company>
<quarter>Q3 2020</quarter>
<net_income>13953656</net_income>
</financial_report>


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Transform this XML data into TOML format:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Synchronized holistic archive API</title>
<version>1.0.0</version>
</info>
<paths>
</policy>
<get>
<summary>Red reason present loss yeah run.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//policy>
</paths>
</api_specification>

[Assistant]
Approach:
1. Task: Convert api specification from XML to TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
openapi = "3.0.0"

[info]
title = "Synchronized holistic archive API"
version = "1.0.0"

[paths."/policy".get]
summary = "Red reason present loss yeah run."
[[paths."/policy".get.parameters]]
name = "param0"
in = "query"
type = "string"

[paths."/policy".get.responses.200]
description = "Success"

[paths."/policy".get.responses.400]
description = "Bad Request"


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of prescription.

[Assistant]
Approach:
1. Task: Create prescription in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "rx_id": "RX-3305496",
  "patient_mrn": "MRN-551064",
  "prescriber": "Eric Jackson",
  "date": "2026-01-03",
  "medications": [
    {
      "name": "Atorvastatin",
      "dosage": "20mg",
      "frequency": "daily",
      "quantity": 90
    }
  ]
}


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Create a YAML representation of experiment result.

[Assistant]
Approach:
1. Task: Create experiment result in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
experiment_id: EXP-506156
title: Effect of window on soldier
methodology:
  design: observational
  sample_size: 884
  duration_days: 87
results:
- metric: safety
  baseline: 32.86
  endpoint: 81.82
  p_value: 0.3265
- metric: efficacy
  baseline: 88.84
  endpoint: 10.2
  p_value: 0.448
- metric: safety
  baseline: 27.68
  endpoint: 60.55
  p_value: 0.1062
- metric: safety
  baseline: 51.8
  endpoint: 89.23
  p_value: 0.4543
conclusion: significant


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Create a YAML representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
review_id: REV-2691236
product_id: PROD-245093
user_id: 98b0ec97-f0e6-4eda-907b-c1488d5de2f5
rating: 1
title: Now new sell exist just.
content: 'Issue suddenly such maybe. Military they second staff end agreement.

  Close that speech alone know wish matter. Finally adult statement method.'
date: '2026-01-02'
verified_purchase: false
helpful_votes: 34


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "company": "Thompson, Yang and Roberts",
  "ticker": "ATOM",
  "quarter": "Q1 2022",
  "revenue": 59725729,
  "expenses": 36274579,
  "net_income": 7802792,
  "eps": 8.84,
  "metrics": {
    "profit_margin": 17.46,
    "roe": 22.69
  }
}

[Assistant]
Approach:
1. Task: Convert financial report from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Thompson, Yang and Roberts</company>
<ticker>ATOM</ticker>
<quarter>Q1 2022</quarter>
<revenue>59725729</revenue>
<expenses>36274579</expenses>
<net_income>7802792</net_income>
<eps>8.84</eps>
<metrics>
<profit_margin>17.46</profit_margin>
<roe>22.69</roe>
</metrics>
</financial_report>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output student assessment as XML.

[Assistant]
Approach:
1. Task: Create student assessment in XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<date>2026-01-01</date>
<total_score>85</total_score>
<student_id>STU-920172</student_id>
</student_assessment>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Transform this XML data into CSV format:
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>03dcbba2-8070-483e-a807-51e4c6301bf5</error_id>
<timestamp>2026-01-07T13:51:27.875594</timestamp>
<level>WARNING</level>
<service>stockService</service>
<message>Feel garden dark.</message>
<stack_trace>at another.py:304</stack_trace>
<stack_trace>at happy.py:331</stack_trace>
<stack_trace>at record.py:415</stack_trace>
<context>
<user_id>cedcf075-a01b-42e9-acdc-a300ea843992</user_id>
<request_id>acbfd7fd-a4ab-431b-a098-ac4537826f14</request_id>
</context>
</error_log>

[Assistant]
Approach:
1. Task: Convert error log from XML to CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
abstract,authors,citations,context_request_id,context_user_id,error_id,funding_source,keywords,level,message,paper_id,publication_doi,publication_venue,publication_year,service,stack_trace,timestamp,title
,,,acbfd7fd-a4ab-431b-a098-ac4537826f14,cedcf075-a01b-42e9-acdc-a300ea843992,03dcbba2-8070-483e-a807-51e4c6301bf5,,,WARNING,Feel garden dark.,,,,,stockService,"[""at another.py:304"", ""at happy.py:331"", ""at record.py:415""]",2026-01-07T13:51:27.875594,
Kid quality happen leave economy learn sit. Major remember floor within manage son must. Upon manage,"[{""name"": ""Bradley Ward"", ""affiliation"": ""Ibarra, Perkins and Strickland"", ""email"": ""brittney36@exam",255,,,,Owen Ltd,"[""family"", ""plan"", ""seem"", ""night""]",,,arXiv:2023.57213,10.5866/NKXo,Nature,2022,,,,Digitized modular alliance
Drive many individual understand time continue. Represent support ready director. Green entire howev,"[{""name"": ""James Fischer"", ""affiliation"": ""Martinez, Melendez and Cameron"", ""email"": ""sjenkins@examp",466,,,,Gibbs Ltd,"[""sing"", ""range"", ""month"", ""successful""]",,,arXiv:2022.61325,10.2274/NejD,Nature,2023,,,,Open-source responsive utilization
Assume ready surface laugh. Memory worker structure either itself detail law.,"[{""name"": ""Dennis Bradshaw"", ""affiliation"": ""Barnes-Ray"", ""email"": ""richardwood@example.org""}, {""nam",418,,,,None,"[""citizen"", ""green"", ""eight"", ""ask""]",,,arXiv:2020.17827,10.5988/DiCF,Nature,2022,,,,Progressive multimedia time-frame


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output news article as CSV.

[Assistant]
Approach:
1. Task: Create news article in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
article_id,author,content,headline,published,section,shares,tags,views
ART-8668047,Alyssa Moore,"Billion up year window similar. Oil two resource next. If this tough pattern.
Rule year push interna",Seamless local alliance,2026-01-02T06:22:52.413807,Business,3713,"[""traditional"", ""wish"", ""little"", ""inside"", ""year""]",55093
ART-9186075,Anthony Hernandez,Control manage popular but suffer within. Size agreement they much. You mean process determine occur,Synchronized intermediate capability,2026-01-07T02:14:37.387739,Politics,1548,"[""way"", ""rest"", ""meet""]",14504
ART-1983056,David Hogan,"Occur environment operation network high result me. Meeting game from space perhaps.
Special these l",Multi-lateral uniform Graphical User Interface,2026-01-02T04:00:24.249660,Tech,1930,"[""student"", ""meet"", ""page""]",55569
ART-4083492,Julian Wong,"Land cup director similar source make put through. Travel sound sport machine.
Join decade managemen",Profit-focused needs-based support,2026-01-02T22:17:44.304849,Politics,972,"[""whose"", ""song"", ""speak"", ""evening"", ""recently""]",27239
ART-6678076,Jordan Walker,"Describe present gun floor PM always or. Cause water consumer number at.
West sport dog its agency y",Re-contextualized real-time groupware,2026-01-07T00:37:46.612036,Politics,485,"[""much"", ""writer"", ""its"", ""read""]",69365


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Output lab result as TOML.

[Assistant]
Approach:
1. Task: Create lab result in TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
order_date = "2026-01-01"
panel = "Lipid"
patient_mrn = "MRN-952425"
result_id = "LAB-8958063"
[[results]]
test = "Glucose"
value = 142.4
unit = "g/dL"
flag = "normal"

[[results]]
test = "Hemoglobin"
value = 196.3
unit = "g/dL"
flag = "normal"

[[results]]
test = "Hemoglobin"
value = 74.4
unit = "mg/dL"
flag = "normal"

[[results]]
test = "Hemoglobin"
value = 119.9
unit = "mg/dL"
flag = "high"

[[results]]
test = "WBC"
value = 99.2
unit = "mg/dL"
flag = "normal"

[[results]]
test = "Glucose"
value = 51.3
unit = "g/dL"
flag = "normal"

[[results]]
test = "Glucose"
value = 186.5
unit = "mg/dL"
flag = "low"


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "review_id": "REV-1132090",
  "product_id": "PROD-380257",
  "user_id": "251dc214-da1e-4fb5-8ea5-d107ad43f82c",
  "rating": 4,
  "title": "Young race true property less government.",
  "content": "Brother agent radio might own development. Too strong minute building why. Cell so amount imagine simple.\nCourt every deal change allow last practice. Western far thus.",
  "date": "2026-01-03",
  "verified_purchase": false,
  "helpful_votes": 14
}

[Assistant]
Approach:
1. Task: Convert customer review from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-1132090</review_id>
<product_id>PROD-380257</product_id>
<user_id>251dc214-da1e-4fb5-8ea5-d107ad43f82c</user_id>
<rating>4</rating>
<title>Young race true property less government.</title>
<content>Brother agent radio might own development. Too strong minute building why. Cell so amount imagine simple.
Court every deal change allow last practice. Western far thus.</content>
<date>2026-01-03</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>14</helpful_votes>
</customer_review>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
course_id: CRS-3741
code: XMJ312
title: Managed incremental focus group 101
instructor: Rachel Diaz
credits: 4
term: Fall 2021
schedule:
- week: 1
  topic: body
- week: 2
  topic: rather
- week: 3
  topic: song
- week: 4
  topic: child
- week: 5
  topic: born
- week: 6
  topic: beyond
- week: 7
  topic: there
grading:
  homework: 30
  midterm: 30
  final: 40


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-7250124</review_id>
<product_id>PROD-375265</product_id>
<user_id>48302d32-0445-4405-afc6-604ef6300782</user_id>
<rating>1</rating>
<title>Very responsibility coach economy sea public you.</title>
<content>Chair painting shake city kind good though. Find reality water support key.
Fly party couple production fight. Live attention anyone her traditional. I room blood condition research fund model.</content>
<date>2026-01-03</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>78</helpful_votes>
</customer_review>

[Assistant]
Approach:
1. Task: Convert customer review from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "review_id": "REV-7250124",
  "product_id": "PROD-375265",
  "user_id": "48302d32-0445-4405-afc6-604ef6300782",
  "rating": 1,
  "title": "Very responsibility coach economy sea public you.",
  "content": "Chair painting shake city kind good though. Find reality water support key.\nFly party couple production fight. Live attention anyone her traditional. I room blood condition research fund model.",
  "date": "2026-01-03",
  "verified_purchase": true,
  "helpful_votes": 78
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output customer review as XML.

[Assistant]
Approach:
1. Task: Create customer review in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-3637179</review_id>
<product_id>PROD-905516</product_id>
<user_id>cbc145e7-7f32-438c-ba90-61711bf65a15</user_id>
<rating>1</rating>
<title>Hand ok join you population.</title>
<content>Develop particularly receive thing process sister source. Ago short fact start meeting note need. However music factor my million scene use.</content>
<date>2026-01-03</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>42</helpful_votes>
</customer_review>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Convert the following XML to YAML:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-299234</contract_id>
<parties>
<name>Murphy, Hawkins and Mckenzie</name>
<role>party_a</role>
</parties>
<parties>
<name>Collins-Miller</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-06</effective_date>
<term_months>46</term_months>
<value>506357</value>
<status>pending</status>
</contract>

[Assistant]
Approach:
1. Task: Convert contract from XML to YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
contract_id: CTR-299234
parties:
- name: Murphy, Hawkins and Mckenzie
  role: party_a
- name: Collins-Miller
  role: party_b
effective_date: '2026-01-06'
term_months: 46
value: 506357
status: pending


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Transform this CSV data into JSON format:
category,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase
,"Near season take foot decade hold some meet.
Pretty season exist old turn consumer particularly star",,2026-01-02,62,,,,PROD-688379,3,REV-5832770,,,,,Investment great beat fear step Democrat treat.,d5e035fb-55b8-4fae-85aa-504fb2b837bd,False
books,,USD,,,True,Vision-oriented motivating orchestration,148.52,PROD-832459,2.41,,399,47x77x29cm,8.47,69,,,
clothing,,USD,,,True,Organic impactful core,173.15,PROD-638457,2.97,,963,24x99x63cm,6.15,465,,,

[Assistant]
Approach:
1. Task: Convert customer review from CSV to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "review_id": "REV-5832770",
  "product_id": "PROD-688379",
  "user_id": "d5e035fb-55b8-4fae-85aa-504fb2b837bd",
  "rating": 3,
  "title": "Investment great beat fear step Democrat treat.",
  "content": "Near season take foot decade hold some meet.\nPretty season exist old turn consumer particularly star. Step receive unit different.",
  "date": "2026-01-02",
  "verified_purchase": false,
  "helpful_votes": 62
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "note_id": "CN-7937835",
  "patient": {
    "mrn": "MRN-749785",
    "age": 66,
    "gender": "M"
  },
  "encounter_date": "2026-01-06",
  "chief_complaint": "chest pain",
  "vitals": {
    "bp": "179/85",
    "hr": 81,
    "temp_f": 101.7
  },
  "assessment": [
    {
      "problem": "hypertension",
      "icd10": "I52"
    },
    {
      "problem": "diabetes",
      "icd10": "J76"
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert clinical note from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-7937835</note_id>
<patient>
<mrn>MRN-749785</mrn>
<age>66</age>
<gender>M</gender>
</patient>
<encounter_date>2026-01-06</encounter_date>
<chief_complaint>chest pain</chief_complaint>
<vitals>
<bp>179/85</bp>

81

<temp_f>101.7</temp_f>
</vitals>
<assessment>
<problem>hypertension</problem>
<icd10>I52</icd10>
</assessment>
<assessment>
<problem>diabetes</problem>
<icd10>J76</icd10>
</assessment>
</clinical_note>


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Create a TOML representation of financial report.

[Assistant]
Approach:
1. Task: Create financial report in TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
expenses = 65628233
eps = 5.75
quarter = "Q2 2023"
revenue = 73745517
net_income = 6367407


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Convert the following JSON to CSV:
{
  "rating": 2,
  "verified_purchase": true,
  "helpful_votes": 29,
  "date": "2026-01-01",
  "user_id": "ed843147-0604-46c9-98b2-def8aa0c8a20"
}

[Assistant]
Approach:
1. Task: Convert customer review from JSON to CSV
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
abstract,authors,citations,date,funding_source,helpful_votes,keywords,paper_id,publication_doi,publication_venue,publication_year,rating,title,user_id,verified_purchase
,,,2026-01-01,,29,,,,,,2,,ed843147-0604-46c9-98b2-def8aa0c8a20,True
Most local here bag determine style success. Manager test politics push page today. Late bank step P,"[{""name"": ""Melissa Mcneil"", ""affiliation"": ""Jones, Lindsey and Chapman"", ""email"": ""cindyschroeder@ex",188,,None,,"[""who"", ""Mrs"", ""return""]",arXiv:2021.47194,10.2445/FRyK,Cell,2022,,Fully-configurable client-driven matrices,,
"World mother room environment.
Up there rule tonight then raise. Reveal themselves probably sometime","[{""name"": ""Allison Jones"", ""affiliation"": ""Turner, Cabrera and Johnson"", ""email"": ""marshmichael@exam",362,,Williams-Adams,,"[""same"", ""ten"", ""or"", ""listen""]",arXiv:2023.98741,10.7125/AJDL,Science,2022,,Focused zero administration interface,,
Find instead soldier than beautiful important. Run successful address run.,"[{""name"": ""John Pierce"", ""affiliation"": ""Lopez-Casey"", ""email"": ""morrisjames@example.org""}, {""name"":",288,,"Smith, Steele and Richardson",,"[""politics"", ""when"", ""human"", ""century""]",arXiv:2024.80910,10.6835/pbxd,Cell,2023,,Reduced stable matrix,,


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Transform this JSON data into CSV format:
{
  "rx_id": "RX-8706225",
  "patient_mrn": "MRN-970748",
  "prescriber": "Brady Keller",
  "date": "2026-01-01",
  "medications": [
    {
      "name": "Lisinopril",
      "dosage": "5mg",
      "frequency": "TID",
      "quantity": 30
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert prescription from JSON to CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
date,medications,patient_mrn,prescriber,rx_id
2026-01-01,"[{""name"": ""Lisinopril"", ""dosage"": ""5mg"", ""frequency"": ""TID"", ""quantity"": 30}]",MRN-970748,Brady Keller,RX-8706225
2026-01-03,"[{""name"": ""Atorvastatin"", ""dosage"": ""20mg"", ""frequency"": ""daily"", ""quantity"": 90}, {""name"": ""Metform",MRN-914281,Ashley Duarte,RX-7590923
2026-01-05,"[{""name"": ""Metformin"", ""dosage"": ""10mg"", ""frequency"": ""daily"", ""quantity"": 30}, {""name"": ""Metformin""",MRN-251528,Andre Allen,RX-2945300
2026-01-04,"[{""name"": ""Atorvastatin"", ""dosage"": ""20mg"", ""frequency"": ""TID"", ""quantity"": 60}]",MRN-204037,Allen Carroll,RX-4953586
2026-01-04,"[{""name"": ""Atorvastatin"", ""dosage"": ""10mg"", ""frequency"": ""BID"", ""quantity"": 30}, {""name"": ""Metformin",MRN-801020,Calvin Gibbs DDS,RX-7400577


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a customer review.

[Assistant]
Approach:
1. Task: Create customer review in YAML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
rating: 2
verified_purchase: true
helpful_votes: 29
date: '2026-01-01'
user_id: ed843147-0604-46c9-98b2-def8aa0c8a20


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output lab result as CSV.

[Assistant]
Approach:
1. Task: Create lab result in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
order_date,panel,patient_mrn,result_id,results
2026-01-06,CMP,MRN-584871,LAB-5383313,"[{""test"": ""Glucose"", ""value"": 194.0, ""unit"": ""g/dL"", ""flag"": ""normal""}, {""test"": ""Hemoglobin"", ""valu"
2026-01-05,CMP,MRN-557806,LAB-2465863,"[{""test"": ""Glucose"", ""value"": 80.1, ""unit"": ""g/dL"", ""flag"": ""normal""}, {""test"": ""WBC"", ""value"": 107."
2026-01-06,CMP,MRN-914594,LAB-6512945,"[{""test"": ""WBC"", ""value"": 141.6, ""unit"": ""g/dL"", ""flag"": ""high""}, {""test"": ""Glucose"", ""value"": 71.9,"


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-723394</product_id>
<name>Streamlined full-range ability</name>
<category>clothing</category>
<price>959.9</price>
<currency>USD</currency>
<stock>28</stock>
<is_available>True</is_available>
<rating>3.7</rating>
<reviews>332</reviews>
<specs>
<weight_kg>9.93</weight_kg>
<dimensions>53x67x45cm</dimensions>
</specs>
</product_listing>

[Assistant]
Approach:
1. Task: Convert product listing from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "product_id": "PROD-723394",
  "name": "Streamlined full-range ability",
  "category": "clothing",
  "price": 959.9,
  "currency": "USD",
  "stock": 28,
  "is_available": true,
  "rating": 3.7,
  "reviews": 332,
  "specs": {
    "weight_kg": 9.93,
    "dimensions": "53x67x45cm"
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "course_id": "CRS-3948",
  "code": "CSZ142",
  "title": "Intuitive foreground functionalities 101",
  "instructor": "Robert Carter",
  "credits": 4,
  "term": "Fall 2022",
  "schedule": [
    {
      "week": 1,
      "topic": "manage"
    },
    {
      "week": 2,
      "topic": "catch"
    },
    {
      "week": 3,
      "topic": "people"
    },
    {
      "week": 4,
      "topic": "out"
    },
    {
      "week": 5,
      "topic": "story"
    },
    {
      "week": 6,
      "topic": "share"
    },
    {
      "week": 7,
      "topic": "become"
    },
    {
      "week": 8,
      "topic": "part"
    },
    {
      "week": 9,
      "topic": "cell"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}

[Assistant]
Approach:
1. Task: Convert course syllabus from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-3948</course_id>
CSZ142
<title>Intuitive foreground functionalities 101</title>
<instructor>Robert Carter</instructor>
<credits>4</credits>
<term>Fall 2022</term>
<schedule>
<week>1</week>
<topic>manage</topic>
</schedule>
<schedule>
<week>2</week>
<topic>catch</topic>
</schedule>
<schedule>
<week>3</week>
<topic>people</topic>
</schedule>
<schedule>
<week>4</week>
<topic>out</topic>
</schedule>
<schedule>
<week>5</week>
<topic>story</topic>
</schedule>
<schedule>
<week>6</week>
<topic>share</topic>
</schedule>
<schedule>
<week>7</week>
<topic>become</topic>
</schedule>
<schedule>
<week>8</week>
<topic>part</topic>
</schedule>
<schedule>
<week>9</week>
<topic>cell</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Generate financial report data in YAML format.

[Assistant]
Approach:
1. Task: Create financial report in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
company: Harris Inc
ticker: KXNS
quarter: Q2 2023
revenue: 96096321
expenses: 36366080
net_income: 6859279
eps: 2.68
metrics:
  profit_margin: 18.37
  roe: 11.92


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from YAML to JSON:
txn_id: TXN-15638187
customer_id: 242fd3fb-d1fb-4e06-b998-4ca6fd25c6b7
timestamp: '2026-01-07T13:51:27.047573'
items:
- sku: SKU-16950
  qty: 3
  price: 120.22
- sku: SKU-76122
  qty: 1
  price: 377.76
- sku: SKU-41194
  qty: 3
  price: 254.19
- sku: SKU-75246
  qty: 2
  price: 418.85
subtotal: 1338.06
tax: 172.92
total: 2048.81
payment_method: apple_pay

[Assistant]
Approach:
1. Task: Convert transaction record from YAML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "txn_id": "TXN-15638187",
  "customer_id": "242fd3fb-d1fb-4e06-b998-4ca6fd25c6b7",
  "timestamp": "2026-01-07T13:51:27.047573",
  "items": [
    {
      "sku": "SKU-16950",
      "qty": 3,
      "price": 120.22
    },
    {
      "sku": "SKU-76122",
      "qty": 1,
      "price": 377.76
    },
    {
      "sku": "SKU-41194",
      "qty": 3,
      "price": 254.19
    },
    {
      "sku": "SKU-75246",
      "qty": 2,
      "price": 418.85
    }
  ],
  "subtotal": 1338.06,
  "tax": 172.92,
  "total": 2048.81,
  "payment_method": "apple_pay"
}


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Produce a CSV document for a social media post.

[Assistant]
Approach:
1. Task: Create social media post in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
content,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username
Knowledge between friend wife property kid out. Trouble recent member sort arrive foot space good.,95,2564,187,"[""#daughter"", ""#after"", ""#affect"", ""#goal""]",instagram,POST-49469407,2026-01-07T13:51:26.031233,c776cd7c-2538-4c81-83c8-03afd724bed1,donald18
Read truth amount buy music environment. Industry threat recent rest mission available. Analysis fin,100,3055,707,"[""#car"", ""#other"", ""#arm"", ""#a""]",facebook,POST-84408018,2026-01-07T13:51:26.033345,e06ceb36-6ff7-414f-b6eb-3a138910227b,mholt
"Democratic month size toward store.
Get choice she management fill really beautiful. Reality cup phy",210,6055,744,"[""#amount"", ""#manager"", ""#since""]",instagram,POST-29466088,2026-01-07T13:51:26.033893,ed4d4ccd-1c65-4883-a35e-d5d6ff806ad4,murraypaul
Under simple foot while huge might against. Enjoy able employee magazine beyond game least. Central ,194,6074,989,"[""#there"", ""#stock"", ""#carry"", ""#attention""]",instagram,POST-54696778,2026-01-07T13:51:26.034607,8c219d0e-f564-4f06-b9b6-a8bcd81019ff,blairneil


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "note_id": "CN-1129442",
  "patient": {
    "mrn": "MRN-895859",
    "age": 79,
    "gender": "M"
  },
  "encounter_date": "2026-01-03",
  "chief_complaint": "headache",
  "vitals": {
    "bp": "127/81",
    "hr": 117,
    "temp_f": 102.4
  },
  "assessment": [
    {
      "problem": "hypertension",
      "icd10": "J46"
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert clinical note from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-1129442</note_id>
<patient>
<mrn>MRN-895859</mrn>
<age>79</age>
<gender>M</gender>
</patient>
<encounter_date>2026-01-03</encounter_date>
<chief_complaint>headache</chief_complaint>
<vitals>
<bp>127/81</bp>

117

<temp_f>102.4</temp_f>
</vitals>
<assessment>
<problem>hypertension</problem>
<icd10>J46</icd10>
</assessment>
</clinical_note>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of error log.

[Assistant]
Approach:
1. Task: Create error log in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>3ee04eb7-6a96-4708-8070-7816402d081f</error_id>
<timestamp>2026-01-07T13:51:26.236854</timestamp>
<level>ERROR</level>
<service>checkService</service>
<message>Base information cell production decade back.</message>
<stack_trace>at quality.py:463</stack_trace>
<stack_trace>at but.py:317</stack_trace>
<context>
<user_id>9d5113f2-65b2-4f61-b9b2-2b011fc1bc1b</user_id>
<request_id>f5a78ca9-3dcc-4c14-bcea-f5b7936cdde5</request_id>
</context>
</error_log>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate student assessment data in CSV format.

[Assistant]
Approach:
1. Task: Create student assessment in CSV
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
assessment_id,course_id,date,grade,percentage,scores,student_id,total_score,type
ASMT-810488,,,,51.02,,,65,
ASMT-409975,CRS-2271,2026-01-01,B,70.13,"[{""question"": 1, ""points_earned"": 5, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 8, ""po",STU-610603,66,exam
ASMT-225420,CRS-3299,2026-01-06,C,50.04,"[{""question"": 1, ""points_earned"": 6, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 7, ""po",STU-391847,82,assignment
ASMT-687595,CRS-5319,2026-01-04,B,83.21,"[{""question"": 1, ""points_earned"": 7, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 10, ""p",STU-807802,84,assignment
ASMT-613043,CRS-1031,2026-01-04,B,81.87,"[{""question"": 1, ""points_earned"": 5, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 2, ""po",STU-325536,57,assignment


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Create a YAML representation of sales analytics.

[Assistant]
Approach:
1. Task: Create sales analytics in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
period: June 2024
total_revenue: 5319249
units_sold: 96009
channels:
- name: wholesale
  revenue: 941227
  growth: 26.4
- name: retail
  revenue: 937409
  growth: 30.07
top_products:
- sku: SKU-2900
  sales: 81858
- sku: SKU-8266
  sales: 123988
- sku: SKU-9969
  sales: 32400


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of api specification.

[Assistant]
Approach:
1. Task: Create api specification in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Sharable solution-oriented migration API",
    "version": "1.0.0"
  },
  "paths": {
    "/anything": {
      "get": {
        "summary": "Those all evidence respond she listen.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Output customer review as JSON.

[Assistant]
Approach:
1. Task: Create customer review in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "review_id": "REV-4787173",
  "product_id": "PROD-746934",
  "user_id": "a1638e54-91af-4e5f-be10-465327f3fbf6",
  "rating": 4,
  "title": "Rock company surface either million.",
  "content": "Suddenly plant stay thank project hand me. Commercial his road carry training trip.",
  "date": "2026-01-02",
  "verified_purchase": true,
  "helpful_votes": 3
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Output research paper as TOML.

[Assistant]
Approach:
1. Task: Create research paper in TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
paper_id = "arXiv:2024.49729"
title = "Optimized fault-tolerant monitoring"
abstract = "Relate make read game soldier new. Agree south attorney one century drive draw.\nReduce head tax certainly offer deal. Sister station adult seat wear."
keywords = [ "gas", "understand", "everything", "miss",]
citations = 65
funding_source = "Parsons Inc"
[[authors]]
name = "Ashley Hubbard"
affiliation = "Mcdonald-White"
email = "jenniferlong@example.net"

[[authors]]
name = "Erica Marshall"
affiliation = "Calderon-Dalton"
email = "adouglas@example.org"

[[authors]]
name = "Mercedes Campbell"
affiliation = "Davis-Lynch"
email = "yharris@example.org"

[publication]
venue = "Cell"
year = 2024
doi = "10.3465/hMKF"


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a research paper.

[Assistant]
Approach:
1. Task: Create research paper in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
paper_id: arXiv:2024.31964
title: Optimized solution-oriented success
authors:
- name: Meagan Sutton
  affiliation: Williamson, Mitchell and Smith
  email: davilabridget@example.com
- name: William Gross
  affiliation: Miller and Sons
  email: linda03@example.net
abstract: Price while never. Night great must well remain. Share less reveal often.
keywords:
- less
- radio
- spend
- which
publication:
  venue: Science
  year: 2023
  doi: 10.4651/vEqE
citations: 155
funding_source: null


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of financial report.

[Assistant]
Approach:
1. Task: Create financial report in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Ortega-Owens</company>
<ticker>YLLB</ticker>
<quarter>Q3 2022</quarter>
<revenue>37598920</revenue>
<expenses>44591506</expenses>
<net_income>3197580</net_income>
<eps>1.51</eps>
<metrics>
<profit_margin>5.54</profit_margin>
<roe>6.32</roe>
</metrics>
</financial_report>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Pre-emptive interactive encryption API",
    "version": "1.0.0"
  },
  "paths": {
    "/air": {
      "get": {
        "summary": "Final democratic whatever event director guy.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}

[Assistant]
Approach:
1. Task: Convert api specification from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Pre-emptive interactive encryption API</title>
<version>1.0.0</version>
</info>
<paths>
</air>
<get>
<summary>Final democratic whatever event director guy.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//air>
</paths>
</api_specification>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following CSV to XML:
assessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f
"[{""problem"": ""hypertension"", ""icd10"": ""K44""}]",fever,2026-01-04,CN-2804449,73,F,MRN-394213,162/64,70,102.7
"[{""problem"": ""diabetes"", ""icd10"": ""I45""}, {""problem"": ""diabetes"", ""icd10"": ""I27""}, {""problem"": ""hype",fever,2026-01-05,CN-6112078,86,F,MRN-255063,101/79,110,98.0
"[{""problem"": ""hypertension"", ""icd10"": ""I14""}]",chest pain,2026-01-04,CN-4468069,35,F,MRN-183820,161/77,115,100.1
"[{""problem"": ""hypertension"", ""icd10"": ""J19""}, {""problem"": ""hypertension"", ""icd10"": ""I56""}, {""problem",fever,2026-01-04,CN-3630850,19,F,MRN-470813,149/93,69,99.5

[Assistant]
Approach:
1. Task: Convert clinical note from CSV to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-2804449</note_id>
<patient>
<mrn>MRN-394213</mrn>
<age>73</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-04</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>162/64</bp>

70

<temp_f>102.7</temp_f>
</vitals>
<assessment>
<problem>hypertension</problem>
<icd10>K44</icd10>
</assessment>
</clinical_note>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "article_id": "ART-2388619",
  "headline": "Switchable tertiary collaboration",
  "author": "Paula Martinez",
  "published": "2026-01-07T02:15:35.006278",
  "section": "Politics",
  "content": "Choice list strong let reason. Education class ok front impact successful. Huge professor happen data image stop. Notice movie reduce everyone among ask already company.\nDoor president he always capital.\nBlack democratic heart read name. Professional billion prepare executive meeting sport.",
  "tags": [
    "hair",
    "democratic",
    "financial",
    "huge",
    "available"
  ],
  "views": 74003,
  "shares": 1794
}

[Assistant]
Approach:
1. Task: Convert news article from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-2388619</article_id>
<headline>Switchable tertiary collaboration</headline>
<author>Paula Martinez</author>
<published>2026-01-07T02:15:35.006278</published>

Politics

<content>Choice list strong let reason. Education class ok front impact successful. Huge professor happen data image stop. Notice movie reduce everyone among ask already company.
Door president he always capital.
Black democratic heart read name. Professional billion prepare executive meeting sport.</content>
<tags>hair</tags>
<tags>democratic</tags>
<tags>financial</tags>
<tags>huge</tags>
<tags>available</tags>
<views>74003</views>
<shares>1794</shares>
</news_article>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Create a YAML representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
product_id: PROD-308726
name: Cross-platform client-server attitude
category: electronics
price: 875.12
currency: USD
stock: 161
is_available: true
rating: 1.18
reviews: 705
specs:
  weight_kg: 37.34
  dimensions: 78x81x41cm


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "assessment_id": "ASMT-871992",
  "student_id": "STU-916232",
  "course_id": "CRS-5865",
  "type": "quiz",
  "date": "2026-01-05",
  "scores": [
    {
      "question": 1,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 0,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 4,
      "points_possible": 10
    },
    {
      "question": 11,
      "points_earned": 5,
      "points_possible": 10
    }
  ],
  "total_score": 83,
  "percentage": 70.57,
  "grade": "B"
}

[Assistant]
Approach:
1. Task: Convert student assessment from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-871992</assessment_id>
<student_id>STU-916232</student_id>
<course_id>CRS-5865</course_id>
<type>quiz</type>
<date>2026-01-05</date>
<scores>
<question>1</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>10</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>4</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>5</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>5</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>0</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>11</question>
<points_earned>5</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>83</total_score>
<percentage>70.57</percentage>
<grade>B</grade>
</student_assessment>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "course_id": "CRS-4164",
  "code": "RVR286",
  "title": "Team-oriented incremental info-mediaries 101",
  "instructor": "Shannon Miller",
  "credits": 3,
  "term": "Fall 2023",
  "schedule": [
    {
      "week": 1,
      "topic": "stuff"
    },
    {
      "week": 2,
      "topic": "professional"
    },
    {
      "week": 3,
      "topic": "hard"
    },
    {
      "week": 4,
      "topic": "rather"
    },
    {
      "week": 5,
      "topic": "lawyer"
    },
    {
      "week": 6,
      "topic": "camera"
    },
    {
      "week": 7,
      "topic": "focus"
    },
    {
      "week": 8,
      "topic": "spend"
    },
    {
      "week": 9,
      "topic": "couple"
    },
    {
      "week": 10,
      "topic": "quickly"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Produce a CSV document for a prescription.

[Assistant]
Approach:
1. Task: Create prescription in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
date,medications,patient_mrn,prescriber,rx_id
2026-01-06,"[{""name"": ""Atorvastatin"", ""dosage"": ""20mg"", ""frequency"": ""daily"", ""quantity"": 90}, {""name"": ""Atorvas",MRN-934255,Danielle Brown,RX-7665793
2026-01-06,"[{""name"": ""Atorvastatin"", ""dosage"": ""5mg"", ""frequency"": ""BID"", ""quantity"": 60}, {""name"": ""Metformin""",MRN-496122,Sean Brown,RX-4083533
2026-01-01,"[{""name"": ""Lisinopril"", ""dosage"": ""20mg"", ""frequency"": ""daily"", ""quantity"": 60}, {""name"": ""Metformin",MRN-441351,Matthew Watson,RX-8477428
2026-01-03,"[{""name"": ""Metformin"", ""dosage"": ""10mg"", ""frequency"": ""TID"", ""quantity"": 90}]",MRN-768997,Thomas Gonzalez,RX-1067293


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output contract as CSV.

[Assistant]
Approach:
1. Task: Create contract in CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
contract_id,effective_date,parties,status,term_months,value
CTR-274282,2026-01-01,"[{""name"": ""Schroeder LLC"", ""role"": ""party_a""}, {""name"": ""Kemp-Jones"", ""role"": ""party_b""}]",active,28,285721
CTR-140680,2026-01-05,"[{""name"": ""Gray-Johnson"", ""role"": ""party_a""}, {""name"": ""Duffy-Ware"", ""role"": ""party_b""}]",pending,49,54718
CTR-526762,2026-01-04,"[{""name"": ""Mills-Mckee"", ""role"": ""party_a""}, {""name"": ""Morton, Jones and Sweeney"", ""role"": ""party_b""",executed,28,148726


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Output api specification as YAML.

[Assistant]
Approach:
1. Task: Create api specification in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
openapi: 3.0.0
info:
  title: Upgradable 4thgeneration middleware API
  version: 1.0.0
paths:
  /pass:
    get:
      summary: Story amount nor bed night get message.
      parameters:
      - name: param0
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a contract.

[Assistant]
Approach:
1. Task: Create contract in YAML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
effective_date: '2026-01-03'
value: 837359
term_months: 24
status: executed


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Generate api specification data in JSON format.

[Assistant]
Approach:
1. Task: Create api specification in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Cross-group bottom-line algorithm API",
    "version": "1.0.0"
  },
  "paths": {
    "/rule": {
      "get": {
        "summary": "Center available level environment per away author",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output error log as CSV.

[Assistant]
Approach:
1. Task: Create error log in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
abstract,authors,citations,context_request_id,context_user_id,error_id,funding_source,keywords,level,message,paper_id,publication_doi,publication_venue,publication_year,service,stack_trace,timestamp,title
,,,95ca942a-a33a-413f-b1a1-a21e12fa0f30,70c0c786-0e43-42b2-8ec7-e975f39a71f7,042db0a1-c9b1-49a9-9d69-5247a8c47159,,,ERROR,Each reality trip red enough tough common.,,,,,whomService,"[""at note.py:398"", ""at purpose.py:452"", ""at onto.py:106"", ""at member.py:439""]",2026-01-07T13:51:27.377057,
Answer single enter teach. Society discuss sure trade reality model.,"[{""name"": ""Raymond Clark"", ""affiliation"": ""Wade-Arroyo"", ""email"": ""stephenshaw@example.com""}, {""name",80,,,,Braun Inc,"[""third"", ""sure"", ""southern""]",,,arXiv:2024.52562,10.5164/sLlJ,Nature,2020,,,,Quality-focused exuding array
Common space inside skin including subject talk. Measure available civil strategy. Just center treat,"[{""name"": ""Michele Martinez"", ""affiliation"": ""Escobar, Yu and Mitchell"", ""email"": ""imiller@example.n",310,,,,"Andrade, Brown and Stokes","[""condition"", ""example"", ""indeed"", ""something"", ""art""]",,,arXiv:2021.10424,10.7741/siSM,Cell,2021,,,,Reduced web-enabled frame
Knowledge common no develop three.,"[{""name"": ""Cynthia Chavez"", ""affiliation"": ""Harris, Gonzalez and Gross"", ""email"": ""sscott@example.co",161,,,,None,"[""house"", ""agent"", ""opportunity""]",,,arXiv:2023.96088,10.3448/HlrR,Science,2024,,,,Optimized attitude-oriented conglomeration


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Convert the following TOML to YAML:
review_id = "REV-1384784"
product_id = "PROD-499626"
user_id = "4c396b1f-b1b7-4ef7-9587-0fda03a6f7f9"
rating = 1
title = "Respond out five."
content = "I stay little Democrat money where stop. Than development activity.\nAlong ahead their standard early nor reason. Fight with minute learn soldier understand."
date = "2026-01-05"
verified_purchase = false
helpful_votes = 94

[Assistant]
Approach:
1. Task: Convert customer review from TOML to YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
review_id: REV-1384784
product_id: PROD-499626
user_id: 4c396b1f-b1b7-4ef7-9587-0fda03a6f7f9
rating: 1
title: Respond out five.
content: 'I stay little Democrat money where stop. Than development activity.

  Along ahead their standard early nor reason. Fight with minute learn soldier understand.'
date: '2026-01-05'
verified_purchase: false
helpful_votes: 94


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2022.73738</paper_id>
<title>Switchable maximized Local Area Network</title>
<authors>
<name>Heather Lee</name>
<affiliation>Garcia, Ellison and Kim</affiliation>
<email>kimberlysimpson@example.com</email>
</authors>
<authors>
<name>Jeremy Gonzalez</name>
<affiliation>Wilson, Sanchez and Copeland</affiliation>
<email>michelle83@example.com</email>
</authors>
<authors>
<name>Brianna Hart</name>
<affiliation>Shannon, Tran and Taylor</affiliation>
<email>penatyler@example.net</email>
</authors>
<abstract>List son shake understand food. Up no police friend factor. Support company yes push argue.</abstract>
<keywords>fact</keywords>
<keywords>guess</keywords>
<keywords>truth</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.7028/ttmb</doi>
</publication>
<citations>36</citations>
<funding_source>Guerra, Richards and Schaefer</funding_source>
</research_paper>

[Assistant]
Approach:
1. Task: Convert research paper from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "paper_id": "arXiv:2022.73738",
  "title": "Switchable maximized Local Area Network",
  "authors": [
    {
      "name": "Heather Lee",
      "affiliation": "Garcia, Ellison and Kim",
      "email": "kimberlysimpson@example.com"
    },
    {
      "name": "Jeremy Gonzalez",
      "affiliation": "Wilson, Sanchez and Copeland",
      "email": "michelle83@example.com"
    },
    {
      "name": "Brianna Hart",
      "affiliation": "Shannon, Tran and Taylor",
      "email": "penatyler@example.net"
    }
  ],
  "abstract": "List son shake understand food. Up no police friend factor. Support company yes push argue.",
  "keywords": [
    "fact",
    "guess",
    "truth"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2024,
    "doi": "10.7028/ttmb"
  },
  "citations": 36,
  "funding_source": "Guerra, Richards and Schaefer"
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output clinical note as XML.

[Assistant]
Approach:
1. Task: Create clinical note in XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<vitals>
<bp>97/107</bp>

107

<temp_f>99.6</temp_f>
</vitals>
<patient>
<mrn>MRN-705297</mrn>
<age>67</age>
<gender>F</gender>
</patient>
<chief_complaint>chest pain</chief_complaint>
<assessment>
<problem>hypertension</problem>
<icd10>K41</icd10>
</assessment>
<assessment>
<problem>hypertension</problem>
<icd10>J91</icd10>
</assessment>
<assessment>
<problem>hypertension</problem>
<icd10>J64</icd10>
</assessment>
<note_id>CN-6154695</note_id>
</clinical_note>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Generate contract data in JSON format.

[Assistant]
Approach:
1. Task: Create contract in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "contract_id": "CTR-291572",
  "parties": [
    {
      "name": "Smith and Sons",
      "role": "party_a"
    },
    {
      "name": "Avila-Campbell",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-03",
  "term_months": 47,
  "value": 297446,
  "status": "pending"
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2024.49729</paper_id>
<title>Optimized fault-tolerant monitoring</title>
<authors>
<name>Ashley Hubbard</name>
<affiliation>Mcdonald-White</affiliation>
<email>jenniferlong@example.net</email>
</authors>
<authors>
<name>Erica Marshall</name>
<affiliation>Calderon-Dalton</affiliation>
<email>adouglas@example.org</email>
</authors>
<authors>
<name>Mercedes Campbell</name>
<affiliation>Davis-Lynch</affiliation>
<email>yharris@example.org</email>
</authors>
<abstract>Relate make read game soldier new. Agree south attorney one century drive draw.
Reduce head tax certainly offer deal. Sister station adult seat wear.</abstract>
<keywords>gas</keywords>
<keywords>understand</keywords>
<keywords>everything</keywords>
<keywords>miss</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.3465/hMKF</doi>
</publication>
<citations>65</citations>
<funding_source>Parsons Inc</funding_source>
</research_paper>

[Assistant]
Approach:
1. Task: Convert research paper from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "paper_id": "arXiv:2024.49729",
  "title": "Optimized fault-tolerant monitoring",
  "authors": [
    {
      "name": "Ashley Hubbard",
      "affiliation": "Mcdonald-White",
      "email": "jenniferlong@example.net"
    },
    {
      "name": "Erica Marshall",
      "affiliation": "Calderon-Dalton",
      "email": "adouglas@example.org"
    },
    {
      "name": "Mercedes Campbell",
      "affiliation": "Davis-Lynch",
      "email": "yharris@example.org"
    }
  ],
  "abstract": "Relate make read game soldier new. Agree south attorney one century drive draw.\nReduce head tax certainly offer deal. Sister station adult seat wear.",
  "keywords": [
    "gas",
    "understand",
    "everything",
    "miss"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2024,
    "doi": "10.3465/hMKF"
  },
  "citations": 65,
  "funding_source": "Parsons Inc"
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Generate product listing data in JSON format.

[Assistant]
Approach:
1. Task: Create product listing in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "product_id": "PROD-107958",
  "name": "Adaptive asynchronous synergy",
  "category": "electronics",
  "price": 349.45,
  "currency": "USD",
  "stock": 717,
  "is_available": true,
  "rating": 1.62,
  "reviews": 33,
  "specs": {
    "weight_kg": 15.32,
    "dimensions": "74x31x68cm"
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output product listing as XML.

[Assistant]
Approach:
1. Task: Create product listing in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-361703</product_id>
<name>Grass-roots methodical neural-net</name>
<category>books</category>
<price>156.58</price>
<currency>USD</currency>
<stock>3</stock>
<is_available>True</is_available>
<rating>3.73</rating>
<reviews>915</reviews>
<specs>
<weight_kg>25.41</weight_kg>
<dimensions>90x40x81cm</dimensions>
</specs>
</product_listing>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-852387</product_id>
<name>Profound logistical array</name>
<category>electronics</category>
<price>299.46</price>
<currency>USD</currency>
<stock>505</stock>
<is_available>True</is_available>
<rating>2.95</rating>
<reviews>519</reviews>
<specs>
<weight_kg>6.22</weight_kg>
<dimensions>16x47x36cm</dimensions>
</specs>
</product_listing>

[Assistant]
Approach:
1. Task: Convert product listing from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "product_id": "PROD-852387",
  "name": "Profound logistical array",
  "category": "electronics",
  "price": 299.46,
  "currency": "USD",
  "stock": 505,
  "is_available": true,
  "rating": 2.95,
  "reviews": 519,
  "specs": {
    "weight_kg": 6.22,
    "dimensions": "16x47x36cm"
  }
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Generate course syllabus data in TOML format.

[Assistant]
Approach:
1. Task: Create course syllabus in TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
course_id = "CRS-4513"
code = "NEE477"
title = "Exclusive bottom-line artificial intelligence 101"
instructor = "Jaime Roman"
credits = 3
term = "Spring 2022"
[[schedule]]
week = 1
topic = "marriage"

[[schedule]]
week = 2
topic = "wonder"

[[schedule]]
week = 3
topic = "system"

[[schedule]]
week = 4
topic = "order"

[[schedule]]
week = 5
topic = "very"

[[schedule]]
week = 6
topic = "laugh"

[[schedule]]
week = 7
topic = "practice"

[[schedule]]
week = 8
topic = "sister"

[[schedule]]
week = 9
topic = "join"

[[schedule]]
week = 10
topic = "expect"

[grading]
homework = 30
midterm = 30
final = 40


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Output transaction record as JSON.

[Assistant]
Approach:
1. Task: Create transaction record in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "txn_id": "TXN-85338602",
  "customer_id": "ea7970e3-49c7-4d3a-bbe0-6c539dc6c3d3",
  "timestamp": "2026-01-07T13:51:25.620781",
  "items": [
    {
      "sku": "SKU-22630",
      "qty": 3,
      "price": 89.97
    }
  ],
  "subtotal": 468.67,
  "tax": 148.91,
  "total": 792.01,
  "payment_method": "apple_pay"
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Create a TOML representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review in TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
rating = 2
verified_purchase = true
helpful_votes = 29
date = "2026-01-01"
user_id = "ed843147-0604-46c9-98b2-def8aa0c8a20"


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>385c5830-2f90-42e3-ae2f-53faace4448a</error_id>
<timestamp>2026-01-07T13:51:26.292009</timestamp>
<level>CRITICAL</level>
<service>almostService</service>
<message>People party agreement mother that investment approach.</message>
<stack_trace>at fight.py:491</stack_trace>
<stack_trace>at city.py:369</stack_trace>
<stack_trace>at statement.py:378</stack_trace>
<context>
<user_id>264dfcb4-39aa-45b1-999f-d115795470f4</user_id>
<request_id>4c579c9e-314d-44f6-9e5a-9c3c95ea5e82</request_id>
</context>
</error_log>

[Assistant]
Approach:
1. Task: Convert error log from XML to JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "error_id": "385c5830-2f90-42e3-ae2f-53faace4448a",
  "timestamp": "2026-01-07T13:51:26.292009",
  "level": "CRITICAL",
  "service": "almostService",
  "message": "People party agreement mother that investment approach.",
  "stack_trace": [
    "at fight.py:491",
    "at city.py:369",
    "at statement.py:378"
  ],
  "context": {
    "user_id": "264dfcb4-39aa-45b1-999f-d115795470f4",
    "request_id": "4c579c9e-314d-44f6-9e5a-9c3c95ea5e82"
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Generate lab result data in XML format.

[Assistant]
Approach:
1. Task: Create lab result in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-4911961</result_id>
<patient_mrn>MRN-250544</patient_mrn>
<order_date>2026-01-03</order_date>
<panel>CBC</panel>
<results>
<test>Hemoglobin</test>
<value>121.1</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>77.4</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>107.3</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>172.8</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>166.2</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>140.6</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>WBC</test>
<value>120.4</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Create a YAML representation of news article.

[Assistant]
Approach:
1. Task: Create news article in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
article_id: ART-3682408
headline: Decentralized stable neural-net
author: Thomas Acevedo
published: '2026-01-01T11:30:40.673887'
section: Business
content: 'Cold trial recognize improve nice between these. Happy herself suggest impact
  tell easy.

  Start movie up social real effort. Onto federal prepare class direction rest.

  News party school five bit. Trouble box year how.

  Pressure respond nature. Prepare ball put happen.'
tags:
- movie
- it
- chance
views: 12438
shares: 1329


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Generate api specification data in XML format.

[Assistant]
Approach:
1. Task: Create api specification in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Sharable solution-oriented migration API</title>
<version>1.0.0</version>
</info>
<paths>
</anything>
<get>
<summary>Those all evidence respond she listen.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//anything>
</paths>
</api_specification>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output news article as CSV.

[Assistant]
Approach:
1. Task: Create news article in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
article_id,author,content,headline,published,section,shares,tags,views
ART-8172649,Rachel Clark,"Pattern capital time compare include night top. Large than important morning.
Card authority protect",Triple-buffered responsive model,2026-01-03T00:35:22.551008,Business,392,"[""consider"", ""whatever"", ""part"", ""however"", ""special""]",49705
ART-7189488,Christine Wilson,"Far six buy seven. Society buy nation opportunity mouth.
Head production college join. Agree few req",Robust tangible application,2026-01-01T13:45:21.050601,Business,2651,"[""unit"", ""of"", ""cold"", ""person"", ""operation""]",28623
ART-7628523,Robert Rosales,"Clearly surface must whose.
State author audience movie tell leg. Find contain begin usually Congres",User-centric uniform forecast,2026-01-02T21:44:28.404414,Politics,4900,"[""position"", ""actually"", ""cause"", ""skill""]",64263


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review in JSON
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "date": "2026-01-04",
  "user_id": "d6e6e646-61a4-4af9-a9a1-d03d234244eb",
  "content": "It herself scene five side support onto. Shake fear western believe. Say fact shoulder investment television pretty suffer.\nGround listen official hand at indeed. Effort thus wife control."
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Output prescription as TOML.

[Assistant]
Approach:
1. Task: Create prescription in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
rx_id = "RX-1995080"
patient_mrn = "MRN-674224"
prescriber = "Emily Herrera"
date = "2026-01-05"
[[medications]]
name = "Lisinopril"
dosage = "10mg"
frequency = "BID"
quantity = 60


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Generate product listing data in TOML format.

[Assistant]
Approach:
1. Task: Create product listing in TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
product_id = "PROD-651261"
name = "Cross-platform scalable protocol"
category = "clothing"
price = 855.77
currency = "USD"
stock = 343
is_available = true
rating = 3.23
reviews = 830

[specs]
weight_kg = 21.29
dimensions = "84x20x91cm"


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Output api specification as YAML.

[Assistant]
Approach:
1. Task: Create api specification in YAML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
openapi: 3.0.0
info:
  title: Synchronized holistic archive API
  version: 1.0.0
paths:
  /policy:
    get:
      summary: Red reason present loss yeah run.
      parameters:
      - name: param0
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Reformat the data below from XML to YAML:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-2281</course_id>
NHA456
<title>Profit-focused mission-critical hardware 101</title>
<instructor>Natalie Middleton</instructor>
<credits>3</credits>
<term>Spring 2024</term>
<schedule>
<week>1</week>
<topic>its</topic>
</schedule>
<schedule>
<week>2</week>
<topic>attorney</topic>
</schedule>
<schedule>
<week>3</week>
<topic>decision</topic>
</schedule>
<schedule>
<week>4</week>
<topic>every</topic>
</schedule>
<schedule>
<week>5</week>
<topic>direction</topic>
</schedule>
<schedule>
<week>6</week>
<topic>player</topic>
</schedule>
<schedule>
<week>7</week>
<topic>city</topic>
</schedule>
<schedule>
<week>8</week>
<topic>everybody</topic>
</schedule>
<schedule>
<week>9</week>
<topic>throw</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>

[Assistant]
Approach:
1. Task: Convert course syllabus from XML to YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
course_id: CRS-2281
code: NHA456
title: Profit-focused mission-critical hardware 101
instructor: Natalie Middleton
credits: 3
term: Spring 2024
schedule:
- week: 1
  topic: its
- week: 2
  topic: attorney
- week: 3
  topic: decision
- week: 4
  topic: every
- week: 5
  topic: direction
- week: 6
  topic: player
- week: 7
  topic: city
- week: 8
  topic: everybody
- week: 9
  topic: throw
grading:
  homework: 30
  midterm: 30
  final: 40


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "paper_id": "arXiv:2021.48279",
  "title": "Operative systemic definition",
  "authors": [
    {
      "name": "Patricia Owens",
      "affiliation": "Pearson, Quinn and Owens",
      "email": "christopher41@example.net"
    },
    {
      "name": "Wayne Boyd",
      "affiliation": "Delacruz-Weaver",
      "email": "powens@example.net"
    },
    {
      "name": "Christopher Castillo",
      "affiliation": "Lawrence-Caldwell",
      "email": "amandacarey@example.com"
    }
  ],
  "abstract": "Tv wear teacher under doctor. Eight mention month argue amount how voice.",
  "keywords": [
    "month",
    "southern",
    "administration"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2021,
    "doi": "10.1648/XIrv"
  },
  "citations": 167,
  "funding_source": null
}

[Assistant]
Approach:
1. Task: Convert research paper from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2021.48279</paper_id>
<title>Operative systemic definition</title>
<authors>
<name>Patricia Owens</name>
<affiliation>Pearson, Quinn and Owens</affiliation>
<email>christopher41@example.net</email>
</authors>
<authors>
<name>Wayne Boyd</name>
<affiliation>Delacruz-Weaver</affiliation>
<email>powens@example.net</email>
</authors>
<authors>
<name>Christopher Castillo</name>
<affiliation>Lawrence-Caldwell</affiliation>
<email>amandacarey@example.com</email>
</authors>
<abstract>Tv wear teacher under doctor. Eight mention month argue amount how voice.</abstract>
<keywords>month</keywords>
<keywords>southern</keywords>
<keywords>administration</keywords>
<publication>
<venue>Cell</venue>
<year>2021</year>
<doi>10.1648/XIrv</doi>
</publication>
<citations>167</citations>
<funding_source />
</research_paper>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output experiment result as XML.

[Assistant]
Approach:
1. Task: Create experiment result in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<experiment_result>
<experiment_id>EXP-506156</experiment_id>
<title>Effect of window on soldier</title>
<methodology>
<design>observational</design>
<sample_size>884</sample_size>
<duration_days>87</duration_days>
</methodology>
<results>
<metric>safety</metric>
<baseline>32.86</baseline>
<endpoint>81.82</endpoint>
<p_value>0.3265</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>88.84</baseline>
<endpoint>10.2</endpoint>
<p_value>0.448</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>27.68</baseline>
<endpoint>60.55</endpoint>
<p_value>0.1062</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>51.8</baseline>
<endpoint>89.23</endpoint>
<p_value>0.4543</p_value>
</results>
<conclusion>significant</conclusion>
</experiment_result>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output experiment result as XML.

[Assistant]
Approach:
1. Task: Create experiment result in XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<experiment_result>
<results>
<metric>efficacy</metric>
<baseline>40.85</baseline>
<endpoint>40.08</endpoint>
<p_value>0.4196</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>82.87</baseline>
<endpoint>28.4</endpoint>
<p_value>0.208</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>74.0</baseline>
<endpoint>18.43</endpoint>
<p_value>0.3638</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>50.48</baseline>
<endpoint>15.59</endpoint>
<p_value>0.1146</p_value>
</results>
<methodology>
<design>observational</design>
<sample_size>351</sample_size>
<duration_days>339</duration_days>
</methodology>
<conclusion>non-significant</conclusion>
</experiment_result>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-3990665</result_id>
<patient_mrn>MRN-508219</patient_mrn>
<order_date>2026-01-04</order_date>
<panel>Lipid</panel>
<results>
<test>Hemoglobin</test>
<value>80.7</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Glucose</test>
<value>90.9</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>138.0</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>WBC</test>
<value>131.3</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Glucose</test>
<value>172.4</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>WBC</test>
<value>151.6</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>188.6</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
</lab_result>

[Assistant]
Approach:
1. Task: Convert lab result from XML to JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "result_id": "LAB-3990665",
  "patient_mrn": "MRN-508219",
  "order_date": "2026-01-04",
  "panel": "Lipid",
  "results": [
    {
      "test": "Hemoglobin",
      "value": 80.7,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Glucose",
      "value": 90.9,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Hemoglobin",
      "value": 138.0,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "WBC",
      "value": 131.3,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Glucose",
      "value": 172.4,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "WBC",
      "value": 151.6,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Hemoglobin",
      "value": 188.6,
      "unit": "g/dL",
      "flag": "high"
    }
  ]
}