prompt stringlengths 196 2.17k | chosen stringlengths 357 2k | rejected stringlengths 24 17.1k |
|---|---|---|
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Transform this CSV data into TOML format:
assessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,stu... | Approach:
1. Task: Convert student assessment from CSV 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:
assessment_id =... | [assessments]
ASMT-554535 = { code = "", course_id = "CRS-9992", credits = "", date = "2026-01-03", grade = "B", grading_final = "", grading_homework = "", grading_midterm = "", instructor = "", percentage = "63.99", schedule = "[{\"question\": 1, \"points_earned\": 9, \"points_possible\": 10}, {\"question\": 2, \"poin... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Generate news article data in CSV format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create news article 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:
article_id,au... | "headline","author","date","category","summary"
"Scientists Discover New Species in Amazon Rainforest","Dr. Elena Martinez","2024-04-05","Science","A team of researchers has identified a previously unknown species of amphibian in the remote regions of the Amazon, highlighting the biodiversity still being uncovered in t... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"review_id": "REV-1521978",
"product_id": "PROD-894495",
"user_id": "0e93d4dc-0d39-4af2-8ec3-d8d1250011b9",
"rating": 4,
"titl... | 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:
<?x... | <review>
<review_id>REV-1521978</review_id>
<product_id>PROD-894495</product_id>
<user_id>0e93d4dc-0d39-4af2-8ec3-d8d1250011b9</user_id>
<rating>4</rating>
<title>Great how data open such.</title>
<content>City not either situation all along might. Under could expect build member. Fish ready onto white majo... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Produce a CSV document for a student assessment.<|im_end|>
<|im_start|>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:
abst... | "Student Name","Assignment 1","Assignment 2","Final Exam","Overall Grade"
"Alex Johnson","85","90","88","87.67"
"Sophia Lee","78","82","91","83.67"
"Michael Chen","92","88","95","91.67"
"Emma Davis","89","94","85","90.00"
"James Wilson","75","80","78","77.67" |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Output product listing as CSV.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create product listing 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:
abstrac... | product_name,price,category,stock_quantity
Laptop Pro X,"$999.99","Electronics",50
Wireless Mouse,"$29.99","Electronics",200
Bluetooth Speaker,"$79.99","Electronics",150
Cotton T-Shirt,"$19.99","Apparel",300
Wooden Desk,"$149.99","Furniture",75
Travel Backpack,"$59.99","Apparel",100
Smartphone Z2,"$899.99","Electronics... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Output lab result as TOML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create lab result 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:
result_id = "LAB-8093004"
... | [[results]]
name = "Blood Glucose"
value = 98
units = "mg/dL"
timestamp = "2023-10-05T08:30:00Z"
[[results]]
name = "Hemoglobin A1c"
value = 5.6
units = "%"
timestamp = "2023-10-05T08:30:00Z"
[[results]]
name = "Cholesterol"
value = 190
units = "mg/dL"
timestamp = "2023-10-05T08:30:00Z" |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate lab result data in JSON format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create lab result 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:
{
"result_... | {
"lab_results": [
{
"patient_id": "P12345",
"test_name": "Complete Blood Count",
"result": 5.8,
"units": "million cells/μL",
"normal_range": "4.0 - 11.0",
"date": "2023-10-05",
"status": "normal"
},
{
"patient_id": "P12345",
"test_name": "Blood Glucos... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Create a XML representation of customer review.<|im_end|>
<|im_start|>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 versi... | <?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<customer_id>12345</customer_id>
<product_id>PROD987</product_id>
<rating>5</rating>
<review_date>2024-04-15</review_date>
<title>Excellent Product!</title>
<content>Great quality and fast delivery. Highly recommend this product to anyone ... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Generate clinical note data in YAML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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:
note_id: CN... | ```yaml
patient_id: "P123456"
date_of_visit: "2023-10-05"
chief_complaint: "Persistent chest pain for 3 days"
history_of_present_illness:
onset: "3 days ago"
location: "Central chest"
radiation: "Radiates to left arm"
character: "Pressure-like"
severity: "7/10"
duration: "Continuous"
exacerbating_factors:... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Produce a XML document for a sales analytics.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create sales analytics 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 versi... | <?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>
<start_date>2023-01-01</start_date>
<end_date>2023-12-31</end_date>
</period>
<region>
<name>North America</name>
<total_revenue>15000000</total_revenue>
<number_of_sales>2450</number_of_sales>
... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Convert the following CSV to YAML:
article_id,author,content,headline,published,section,shares,tags,views
ART-8172649,Rachel Clark,"Pattern capital time compare include night to... | Approach:
1. Task: Convert news article from CSV 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:
article... | articles:
- article_id: ART-8172649
author: Rachel Clark
content: "Pattern capital time compare include night top. Large than important morning.\nCard authority protect"
headline: Triple-buffered responsive model
published: 2026-01-03T00:35:22.551008
section: Business
shares: 392
tags:
... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Produce a TOML document for a student assessment.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create student assessment 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:
assessment_id = "A... | [student]
name = "Alice Johnson"
grade_level = 10
subject = "Mathematics"
assignment = "Final Exam"
[scores]
quiz_1 = 85
quiz_2 = 92
homework_average = 88
project_score = 96
final_exam = 94
[metadata]
date_assigned = "2023-10-15"
due_date = "2023-10-25"
total_points_possible = 100
grade_letter = "A"
[comments]
teach... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Output social media post as JSON.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create social media post 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:
{
"po... | {
"platform": "twitter",
"content": "Just launched our new product! 🚀 Check it out and let us know what you think. #Innovation #NewLaunch",
"hashtags": [
"Innovation",
"NewLaunch"
],
"timestamp": "2024-04-17T12:00:00Z",
"likes": 0,
"retweets": 0,
"comments": 0
} |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2024.31964</paper_id>
<title>Optimized solution-oriented success... | Approach:
1. Task: Convert research paper 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:
{
... | {
"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",
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Produce a XML document for a lab result.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create lab 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=... | <?xml version="1.0" encoding="UTF-8"?>
<LabResult>
<PatientID>123456</PatientID>
<PatientName>John Doe</PatientName>
<DateOfCollection>2023-10-05</DateOfCollection>
<TimeOfCollection>14:30</TimeOfCollection>
<LabName>City General Hospital Laboratory</LabName>
<TestName>Hemoglobin</TestName>
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"experiment_id": "EXP-139463",
"title": "Effect of quite on arm",
"methodology": {
"design": "RCT",
"sample_size": 371,
... | Approach:
1. Task: Convert experiment result 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:
<?x... | <?xml version="1.0" encoding="UTF-8"?>
<experiment>
<experiment_id>EXP-139463</experiment_id>
<title>Effect of quite on arm</title>
<methodology>
<design>RCT</design>
<sample_size>371</sample_size>
<duration_days>284</duration_days>
</methodology>
<results>
<result>
<metric>safety</metri... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<level>ERROR</level>
<service>writeService</service>
<error_id>85223c4c-4b76-4351-95ee-55a24... | Approach:
1. Task: Convert error log from XML to 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. Transform values to match the target format specifications.
Output:
{
"... | {
"error_log": {
"level": "ERROR",
"service": "writeService",
"error_id": "85223c4c-4b76-4351-95ee-55a2460043f3"
}
} |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Generate news article data in CSV format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create news article 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:
article_id... | "headline","author","publication","date","category","summary"
"Scientists Discover New Species in Amazon Rainforest","Dr. Elena Martinez","Nature Today","2024-04-15","Science","A team of researchers has identified a previously unknown species of frog in the Amazon, highlighting the biodiversity still unexplored in the ... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Produce a YAML document for a course syllabus.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create course syllabus 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:
titl... | ```yaml
course_syllabus:
title: "Introduction to Computer Science"
code: "CS101"
semester: "Fall 2024"
instructor:
name: "Dr. Anna Thompson"
email: "anna.thompson@university.edu"
office: "Engineering Building, Room 320"
office_hours: "Tuesday and Thursday, 2:00 PM - 4:00 PM"
course_description... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Create a JSON representation of product listing.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create product listing 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:
{
... | {
"products": [
{
"id": "P001",
"name": "Wireless Bluetooth Headphones",
"price": 99.99,
"category": "Electronics",
"description": "Comfortable wireless headphones with noise cancellation and 20-hour battery life.",
"availability": true,
"brand": "SoundMax",
"rating... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Convert the following CSV to YAML:
code,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title
GDK183,CRS-6873,3,40,30,30,Melinda Thomps... | Approach:
1. Task: Convert course syllabus from CSV 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:
cour... | code: GDK183
course_id: CRS-6873
credits: 3
grading_final: 40
grading_homework: 30
grading_midterm: 30
instructor: Melinda Thompson
schedule: "[{\"week\": 1, \"topic\": \"girl\"}, {\"week\": 2, \"topic\": \"explain\"}, {\"week\": 3, \"topic\": \"center\"}, {\"we"
term: Fall 2020
title: Grass-roots 24/... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Generate social media post data in CSV format.<|im_end|>
<|im_start|>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,en... | "post_id","platform","content","hashtags","likes","shares","comments","timestamp"
"1","Twitter","Just had the most amazing coffee at @localcafe! ☕ Perfect morning vibes 🌅","#coffee,#morningvibes,#localcafe","125","23","14","2023-10-05 08:30:00"
"2","Instagram","Sunrise over the mountains 🏔️ Nature truly inspires. #na... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate sales analytics data in JSON format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create sales analytics 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:
{
"peri... | {
"sales_analytics": {
"quarter": "Q4 2023",
"total_revenue": 1500000,
"region_wise_sales": {
"North": 420000,
"South": 380000,
"East": 350000,
"West": 350000
},
"product_category_sales": {
"Electronics": 700000,
"Clothing": 450000,
"Furniture": 350000
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Generate sales analytics data in XML format.<|im_end|>
<|im_start|>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 ver... | <?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>2023-12</period>
<region>
<name>North America</name>
<total_sales>1250000.00</total_sales>
<average_daily_sales>10416.67</average_daily_sales>
<top_product>
<name>ElectroSmart Device</name>
<sales>450000.00</sales>
<p... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Generate course syllabus data in TOML format.<|im_end|>
<|im_start|>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-6873"
... | [[course]]
title = "Introduction to Computer Science"
code = "CS101"
semester = "Fall 2024"
credits = 3
instructor = "Dr. Elena Martinez"
office = "Science Building, Room 320"
office_hours = "Tue 3-5 PM, Thu 1-3 PM"
email = "elena.martinez@university.edu"
website = "https://cs.university.edu/cs101"
[[course.requiremen... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Output student assessment as CSV.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create student assessment 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:
assessm... | "Student Name","Subject","Score","Grade"
"Alice Johnson","Math","85","B"
"Bob Smith","Science","92","A"
"Carol Davis","Math","78","C"
"David Brown","Science","88","B"
"Emily Clark","Math","95","A" |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Convert the following JSON to XML:
{
"instructor": "Rachel Moreno DVM",
"credits": 4,
"course_id": "CRS-8305",
"title": "Open-architected even-keeled support 101",
"term"... | Approach:
1. Task: Convert course syllabus 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:
... | <course>
<instructor>Rachel Moreno DVM</instructor>
<credits>4</credits>
<course_id>CRS-8305</course_id>
<title>Open-architected even-keeled support 101</title>
<term>Spring 2023</term>
</course> |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Output clinical note as JSON.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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:
{
"note_i... | {
"clinical_note": "Patient presents with persistent cough, fever, and fatigue for the past three days. Physical exam reveals decreased breath sounds in the right lower lobe. Chest X-ray shows consolidation in the right lower lobe consistent with pneumonia. Patient is prescribed azithromycin 500 mg once daily for fiv... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Produce a TOML document for a contract.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create contract 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:
contract_id = "CTR-896633"
e... | ```toml
[contract]
title = "Software Development Agreement"
party_a = "Acme Technologies Inc."
party_b = "Innovate Solutions Ltd."
effective_date = "2023-10-05"
expiry_date = "2024-10-05"
[contract.terms]
development_scope = "Development of a mobile application with user authentication, payment processing, and data sy... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Optional bottom-line complexity API</title>
<... | Approach:
1. Task: Convert api specification 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:
... | {
"openapi": "3.0.0",
"info": {
"title": "Optional bottom-line complexity API",
"version": "1.0.0"
},
"paths": {}
} |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to XML:
{
"contract_id": "CTR-370819",
"parties": [
{
"name": "Stewart, Thompson and Rogers",
"role": "party_a"
},
{
... | Approach:
1. Task: Convert contract 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 versio... | <contract>
<contract_id>CTR-370819</contract_id>
<parties>
<party>
<name>Stewart, Thompson and Rogers</name>
<role>party_a</role>
</party>
<party>
<name>Jackson, Griffin and Flowers</name>
<role>party_b</role>
</party>
</parties>
<effective_date>2026-01-01</effective_date... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Produce a XML document for a clinical note.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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... | <?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<patient_id>123456</patient_id>
<patient_name>John Doe</patient_name>
<date_of_service>2024-04-15</date_of_service>
<provider_id>P001</provider_id>
<provider_name>Dr. Jane Smith</provider_name>
<encounter_type>Outpatient Visit</encounter_typ... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Create a JSON representation of student assessment.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create student assessment 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:
{
... | {
"student": {
"id": "S12345",
"name": "Alice Johnson",
"grade_level": 10,
"subjects": [
{
"subject": "Mathematics",
"score": 87,
"grade": "B+",
"comments": "Strong problem-solving skills; needs improvement in algebraic proofs."
},
{
"subject":... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"rx_id": "RX-7328466",
"patient_mrn": "MRN-740510",
"prescriber": "William Hebert",
"date": "2026-01-04",
"medications": [
... | Approach:
1. Task: Convert prescription 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 ... | <root>
<rx_id>RX-7328466</rx_id>
<patient_mrn>MRN-740510</patient_mrn>
<prescriber>William Hebert</prescriber>
<date>2026-01-04</date>
<medications>
<medication>
<name>Lisinopril</name>
<dosage>20mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medication>
<... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to XML:
{
"content": "Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\nStrong who agai... | Approach:
1. Task: Convert news article 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:
<?x... | <content>Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.\nStrong who against entire.\nKid television artist dream back agency. Need main ago investment job behavior.</content>
<published>2026-01-03T04:54:27.964292</published>
<views>73181</views>
<headline>Visio... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Reformat the data below from YAML to TOML:
date: '2026-01-04'
user_id: d6e6e646-61a4-4af9-a9a1-d03d234244eb
content: 'It herself scene five side support onto. Shake fear western ... | Approach:
1. Task: Convert customer review from YAML 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:
date = "2026... | date = "2026-01-04"
user_id = "d6e6e646-61a4-4af9-a9a1-d03d234244eb"
content = "It herself scene five side support onto. Shake fear western believe. Say\n fact shoulder investment television pretty suffer.\n\nGround listen official hand at indeed. Effort thus wife control." |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"rx_id": "RX-9719971",
"patient_mrn": "MRN-909141",
"prescriber": "Heather Stephens",
"date": "2026-01-05",
"medications": [
... | Approach:
1. Task: Convert prescription 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 ve... | <?xml version="1.0" encoding="UTF-8"?>
<record>
<rx_id>RX-9719971</rx_id>
<patient_mrn>MRN-909141</patient_mrn>
<prescriber>Heather Stephens</prescriber>
<date>2026-01-05</date>
<medications>
<medication>
<name>Atorvastatin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<value>911148</value>
<contract_id>CTR-919818</contract_id>
<parties>
<name>Riggs, Car... | Approach:
1. Task: Convert contract from XML to 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. Transform values to match the target format specifications.
Output:
{
"v... | {
"value": "911148",
"contract_id": "CTR-919818",
"parties": [
{
"name": "Riggs, Carey and Rojas",
"role": "party_a"
},
{
"name": "Mcdowell-Koch",
"role": "party_b"
}
],
"status": "active",
"term_months": 18
} |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Convert the following JSON to XML:
{
"openapi": "3.0.0",
"info": {
"title": "Organic analyzing strategy API",
"version": "1.0.0"
},
"paths": {
"/similar": {
... | 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"?>
<openapi version="3.0.0">
<info>
<title>Organic analyzing strategy API</title>
<version>1.0.0</version>
</info>
<paths>
<path name="/similar">
<get>
<summary>Natural see lot recently.</summary>
<parameters>
<parameter>
... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Produce a YAML document for a social media post.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create social media post 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:
post_... | ---
title: "🌟 Exciting News! 🌟"
content: "Just launched our new feature — easy, fast, and totally fun to use! Whether you're a longtime user or just getting started, this update is for you. 🚀\n\n👉 Tap the link in our bio to try it out today!\n\n#NewFeature #Innovation #SocialMediaMagic"
author: "Alex Johnson"
date:... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Generate error log data in YAML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create error log 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:
error_id: fd2... | errors:
- timestamp: "2023-10-05T14:32:15Z"
level: ERROR
message: "Failed to connect to database: connection timeout"
component: database_client
stack_trace: "java.net.ConnectException: Connection timed out: connect"
source: com.example.database.DbConnector.connect()
- timestamp: "2023-10-05T14:... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-458464</assessment_id>
<student_id>STU-453066</student_i... | Approach:
1. Task: Convert student assessment 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:
{... | {
"assessment_id": "ASMT-458464",
"student_id": "STU-453066",
"course_id": "CRS-7675",
"type": "assignment",
"date": "2026-01-06",
"scores": [
{
"question": "1",
"points_earned": 0,
"points_possible": 10
},
{
"question": "2",
"points_earned": 9,
"points_possib... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Create a YAML representation of transaction record.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create transaction record 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:
txn_... | transaction:
id: "txn_001"
type: "purchase"
amount: 45.99
currency: "USD"
date: "2023-10-05"
description: "Monthly subscription fee"
category: "subscription"
status: "completed"
reference_number: "REF123456"
merchant: "CloudService Inc."
location: "New York, NY" |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Create a YAML representation of transaction record.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create transaction record 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:
i... | transaction:
id: "T123456"
amount: 250.50
currency: "USD"
description: "Monthly subscription fee"
date: "2023-10-05"
category: "Subscription"
type: "debit"
account: "checking"
status: "completed" |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Output lab result as YAML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create lab 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:
result_id: L... | ```yaml
lab_result:
patient_id: "P123456"
test_name: "Complete Blood Count"
result_value: 12.5
units: "mmol/L"
reference_range:
low: 4.0
high: 10.0
result_status: "Normal"
date_performed: "2023-10-05"
lab_name: "City General Hospital Laboratory"
``` |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Convert the following XML to YAML:
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>September 2022</period>
<total_revenue>4880286</total_revenue>
<units_sold>741... | Approach:
1. Task: Convert sales analytics 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:
peri... | sales_analytics:
period: September 2022
total_revenue: 4880286
units_sold: 74173
channels:
- name: retail
revenue: 2000312
growth: 0.96
- name: wholesale
revenue: 3751658
growth: -3.19
top_products:
- sku: SKU-6977
sales: 264067
- sku: SKU-7032
sales: 443161... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Produce a TOML document for a customer review.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create customer review 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:
review_id = "REV-716994... | [review]
customer_name = "Sarah Jenkins"
rating = 5
review_text = "Excellent product! I was very satisfied with the quality and delivery speed. It arrived ahead of schedule and worked perfectly right out of the box. Highly recommend!"
date = "2024-04-15"
helpful_votes = 12
is_verified_purchase = true |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Output contract as CSV.<|im_end|>
<|im_start|>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,effec... | "Contract ID","Party A","Party B","Effective Date","Term Length","Description"
"1001","TechCorp Inc.","Innovate Solutions","2023-01-15","3 years","Software development and maintenance agreement" |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"rx_id": "RX-9458448",
"patient_mrn": "MRN-362998",
"prescriber": "Courtney Hansen",
"date": "2026-01-02",
"medications": [
... | Approach:
1. Task: Convert prescription 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 ve... | <root>
<rx_id>RX-9458448</rx_id>
<patient_mrn>MRN-362998</patient_mrn>
<prescriber>Courtney Hansen</prescriber>
<date>2026-01-02</date>
<medications>
<name>Lisinopril</name>
<dosage>10mg</dosage>
<frequency>BID</frequency>
<quantity>30</quantity>
</medications>
</root> |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-685161</product_id>
<name>Balanced demand-driven capacity</nam... | Approach:
1. Task: Convert product listing 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:
{
... | {
"product_listing": {
"product_id": "PROD-685161",
"name": "Balanced demand-driven capacity",
"category": "clothing",
"price": 554.83,
"currency": "USD",
"stock": 872,
"is_available": true,
"rating": 3.32,
"reviews": 212,
"specs": {
"weight_kg": 39.83,
"dimensions"... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate prescription data in JSON format.<|im_end|>
<|im_start|>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":... | {
"prescription": {
"patient_id": "P123456",
"patient_name": "Alice Johnson",
"date_of_birth": "1985-03-15",
"prescriber_name": "Dr. Michael Chen",
"prescriber_license": "MD-789012",
"prescription_id": "PR-987654",
"date_prescribed": "2024-04-10",
"medication": {
"name": "Atorvas... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Produce a JSON document for a api specification.<|im_end|>
<|im_start|>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:
{
"op... | {
"api": {
"name": "User Management API",
"version": "1.0.0",
"base_url": "https://api.example.com/v1",
"description": "An API for managing user accounts, including creation, authentication, and profile updates.",
"contact": {
"email": "support@example.com",
"url": "https://www.example... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<title>Exactly almost full new record save.</title>
<date>2026-01-02</date>
<product_i... | Approach:
1. Task: Convert customer review from XML to 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. Transform values to match the target format specifications.
Output:... | {
"title": "Exactly almost full new record save.",
"date": "2026-01-02",
"product_id": "PROD-922306",
"content": "Arrive much low will teach. By possible nature learn could. Act hot whole guy experience. Identify world fight stock. Force fear soon. Author night think."
} |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Output social media post as TOML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create social media post 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:
post_id = "POST-46905... | [[post]]
platform = "twitter"
content = "Just shared a 🚀 new feature that's going to change how you interact with content! Check it out link in bio. #innovation #newfeature"
timestamp = "2023-10-05T14:30:00Z"
hashtags = ["innovation", "newfeature"] |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to XML:
{
"instructor": "Tamara Stark",
"term": "Spring 2022",
"code": "VMA483",
"grading": {
"homework": 30,
"midterm": 30,
"... | Approach:
1. Task: Convert course syllabus 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:
... | <instructor>Tamara Stark</instructor>
<term>Spring 2022</term>
<code>VMA483</code>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading> |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Create a YAML representation of financial report.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create financial report 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:
company:... | ```yaml
financial_report:
period: "Q1 2024"
company_name: "TechCorp Inc."
revenue:
amount: 15000000
currency: "USD"
expenses:
research_and_development: 3000000
marketing: 2000000
administrative: 1500000
total: 6500000
profit:
amount: 8500000
currency: "USD"
net_profit_margin:... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Generate social media post data in TOML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create social media post 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:
post_id = "POST-182... | [[post]]
platform = "twitter"
content = "Just launched our new product! 🚀 Check out the features and how it can transform your workflow. More info → https://example.com/new-product"
timestamp = "2023-10-05T14:30:00Z"
hashtags = ["#newproduct", "#innovation", "#launch"]
media = ["https://example.com/image1.jpg", "https... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Output prescription as YAML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create prescription 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:
rx_id: RX-90... | prescription:
patient_name: "John Doe"
date: "2023-10-05"
medication:
name: "Atorvastatin"
dose: "20 mg"
frequency: "once daily"
duration: "30 days"
instructions:
- "Take with food."
- "Do not stop medication without consulting your physician."
refills: 2
signature: "Dr. Alice Smith" |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate clinical note data in JSON format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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:
{
"note_i... | {
"patient_id": "P123456",
"date_of_visit": "2023-10-15",
"chief_complaint": "Persistent chest pain for 3 days",
"history_of_present_illness": "Patient reports dull, aching chest pain radiating to the left shoulder, occurring primarily when climbing stairs or exerting physically. Pain is not associated with exe... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate transaction record data in JSON format.<|im_end|>
<|im_start|>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:
{
"t... | {
"transaction_id": "TXN001234",
"amount": 299.99,
"currency": "USD",
"description": "Monthly subscription fee",
"transaction_date": "2023-10-05",
"category": "Subscription",
"status": "completed",
"source": "Credit Card",
"merchant_name": "CloudService Inc.",
"location": "San Francisco, CA",
"ref... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Convert the following TOML to YAML:
error_id = "92d36993-19b1-4c19-9b64-8b4669c6636f"
timestamp = "2026-01-07T13:51:27.222487"
level = "WARNING"
service = "voiceService"
message ... | Approach:
1. Task: Convert error log 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:
error_id:... | error_id: "92d36993-19b1-4c19-9b64-8b4669c6636f"
timestamp: "2026-01-07T13:51:27.222487"
level: "WARNING"
service: "voiceService"
message: "Analysis beautiful attack blue eye."
stack_trace:
- "at well.py:163"
- "at will.py:421"
- "at run.py:384"
- "at TV.py:103"
context:
user_id: "c92bcb8f-c109-47f8-aa13-b437... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Reformat the data below from CSV to TOML:
abstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title
"Relate make read ... | Approach:
1. Task: Convert research paper from CSV 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:
paper_id = "arXiv:2... | [papers]
"arXiv:2024.49729" = { abstract = "Relate make read game soldier new. Agree south attorney one century drive draw. Reduce head tax cert", authors = [{name = "Ashley Hubbard", affiliation = "Mcdonald-White", email = "jenniferlong@example.net"}, {name = "Shawn Fischer", affiliation = "Leblanc-Long", email = "hol... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate sales analytics data in JSON format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create sales analytics 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:
{
"peri... | {
"sales_analytics": {
"period": "2023-Q4",
"total_revenue": 1250000,
"number_of_orders": 8765,
"average_order_value": 142.67,
"top_performing_product": {
"product_id": "P105",
"product_name": "Premium Wireless Headphones",
"revenue_contribution": 328000,
"units_sold": 2300... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Generate financial report data in YAML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create financial report 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:
company:... | ```yaml
financial_report:
period: "Q1 2024"
company_name: "TechInnovate Inc."
revenue:
total: 15000000
growth_rate: 12.5
expenses:
cost_of_goods_sold: 6000000
operating_expenses: 4500000
administrative_expenses: 1200000
other_expenses: 300000
profit:
gross_profit: 9000000
net_p... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-577861</assessment_id>
<student_id>STU-664280</student_i... | Approach:
1. Task: Convert student assessment 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:... | {
"assessment_id": "ASMT-577861",
"student_id": "STU-664280",
"course_id": "CRS-8099",
"type": "exam",
"date": "2026-01-06",
"scores": [
{
"question": "1",
"points_earned": 7,
"points_possible": 10
},
{
"question": "2",
"points_earned": 0,
"points_possible": 1... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-1797</course_id>
<code>QAA477</code>
<title>User-friendly composite int... | Approach:
1. Task: Convert course syllabus 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:
{
... | {
"course_syllabus": {
"course_id": "CRS-1797",
"code": "QAA477",
"title": "User-friendly composite interface 101",
"instructor": "Selena Walker",
"credits": 4,
"term": "Fall 2024",
"schedule": [
{
"week": 1,
"topic": "all"
},
{
"week": 2,
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Produce a XML document for a clinical note.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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... | <?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<patient_id>PID123456</patient_id>
<patient_name>John A. Smith</patient_name>
<date_of_service>2023-10-05</date_of_service>
<provider_id>PID001</provider_id>
<provider_name>Dr. Emily Carter</provider_name>
<encounter_type>Outpatient Visit</encounter_typ... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Output customer review as TOML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create customer review 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:
review_id = "REV-136997... | [[review]]
author = "John Doe"
rating = 5
title = "Excellent Product!"
content = "I absolutely love this product! It exceeded my expectations in every way. The quality is outstanding, and it arrived quickly. I would definitely recommend it to anyone looking for a reliable and high-performance solution." |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to XML:
{
"rating": 4.54,
"stock": 843,
"specs": {
"weight_kg": 34.7,
"dimensions": "61x86x65cm"
},
"currency": "USD"
}<|im_end|... | Approach:
1. Task: Convert product listing 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"?>
<product>
<rating>4.54</rating>
<stock>843</stock>
<specs>
<weight_kg>34.7</weight_kg>
<dimensions>61x86x65cm</dimensions>
</specs>
<currency>USD</currency>
</product> |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to XML:
{
"contract_id": "CTR-313579",
"parties": [
{
"name": "Roberts, Newton and Ortiz",
"role": "party_a"
},
{
... | Approach:
1. Task: Convert contract 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 versio... | <contract>
<contract_id>CTR-313579</contract_id>
<parties>
<party>
<name>Roberts, Newton and Ortiz</name>
<role>party_a</role>
</party>
<party>
<name>Garcia PLC</name>
<role>party_b</role>
</party>
</parties>
<effective_date>2026-01-01</effective_date>
<term_months>55</... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Generate prescription data in YAML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create prescription 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:
rx_id: RX-90... | prescription:
patient_id: "P123456"
patient_name: "John Doe"
date_of_birth: "1980-05-15"
gender: "Male"
prescription_date: "2023-10-05"
medication_name: "Atorvastatin"
dosage: "20 mg"
frequency: "Daily"
duration: "30 days"
route: "Oral"
strength: "20mg/10mL"
physician_name: "Dr. Emily Smith"
p... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Generate prescription data in TOML format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create prescription 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:
rx_id = "RX-5523111"
... | [prescription]
patient_name = "John Doe"
date_prescribed = "2023-10-05"
drug_name = "Atorvastatin"
dose = "20 mg"
frequency = "once daily"
duration = "30 days"
route = "oral"
instructions = "Take with food"
refills = 3
prescriber_name = "Dr. Jane Smith"
prescriber_license = "MD12345"
pharmacy_name = "City Wellness Phar... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Produce a CSV document for a clinical note.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create clinical note 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:
assessment,chi... | "Date","Time","Provider","Patient Name","Chief Complaint","History of Present Illness","Physical Examination","Diagnosis","Plan"
"2023-10-05","14:30","Dr. Smith","John Doe","Fever and cough","Patient reports febrile onset 3 days ago, productive cough with yellow sputum, mild dyspnea. No chest pain or rash. No recent tr... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Generate course syllabus data in CSV format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create course syllabus 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:
code,course_... | "Course Name","Instructor","Meeting Days","Time","Location","Prerequisites","Textbook","Credit Hours"
"Introduction to Computer Science","Dr. Alice Johnson","Mondays, Wednesdays","10:00 AM - 11:30 AM","Room 205","None","Python Programming: An Introduction to Problem Solving by Mark Lutz",3
"Calculus I","Prof. Robert Ki... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-5347545</article_id>
<headline>Triple-buffered zero administration algori... | Approach:
1. Task: Convert news article 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:
{
"... | {
"article_id": "ART-5347545",
"headline": "Triple-buffered zero administration algorithm",
"author": "Martha Brown",
"published": "2026-01-05T16:28:34.342789",
"section": "Sports",
"content": "Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Create a TOML representation of student assessment.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create student assessment 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:
total_score = 9... | ```toml
[student_assessment]
student_id = "S12345"
name = "Alice Johnson"
grade_level = 10
subject = "Mathematics"
assessment_date = "2023-11-05"
assignment_type = "Midterm Exam"
[scores]
homework = 85
quizzes = 92
midterm = 78
final_exam = 95
[metadata]
total_points_possible = 100
weighted_average = 87.5
grade_lette... |
<|im_start|>system
You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.<|im_end|>
<|im_start|>user
Output error log as YAML.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create error log 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:
error_id: 6b141... | error_log:
timestamp: "2023-10-05T14:30:45Z"
level: ERROR
message: "Failed to connect to database: timeout"
source: "database_connection_module"
stack_trace:
- "at com.example.db.ConnectionManager.connect(ConnectionManager.java:45)"
- "at com.example.service.UserService.login(UserService.java:23)"
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"openapi": "3.0.0",
"info": {
"title": "Horizontal interactive project API",
"version": "1.0.0"
},
"paths": {
"/base... | 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"?>
<openapi version="3.0.0">
<info>
<title>Horizontal interactive project API</title>
<version>1.0.0</version>
</info>
<paths>
<path path="/base">
<get>
<summary>Management send father actually special image.</summary>
<parameters>
<p... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Create a JSON representation of error log.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create error log 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:
{
"error_id... | {
"error_log": [
{
"timestamp": "2023-10-05T14:32:18Z",
"level": "ERROR",
"message": "Failed to connect to database server",
"source": "database_module",
"details": {
"error_code": "DB_CONN_001",
"host": "db-server-01.company.com",
"port": 5432,
"cause... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Generate sales analytics data in JSON format.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create sales analytics 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:
{
"pe... | {
"sales_analytics": {
"period": "2023-Q4",
"total_revenue": 4567890,
"average_order_value": 123.45,
"number_of_orders": 37250,
"top_product_category": "Electronics",
"top_selling_product": "Wireless Headphones",
"region_with_highest_sales": "North America",
"growth_rate": 18.7,
"r... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Transform this JSON data into XML format:
{
"post_id": "POST-86945311",
"platform": "facebook",
"user_id": "b9da037c-f6cd-4ced-8c95-ca7562cf6118",
"username": "martinsteven... | Approach:
1. Task: Convert social media post 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:
<?x... | <post>
<post_id>POST-86945311</post_id>
<platform>facebook</platform>
<user_id>b9da037c-f6cd-4ced-8c95-ca7562cf6118</user_id>
<username>martinsteven</username>
<content>Forget late prevent year cold able arrive. Few possible himself sing community. Activity campaign sure south. Chance on none line best magazi... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Create a CSV representation of research paper.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create research paper 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,auth... | title,authors,institution,year,abstract
"Advancements in Renewable Energy Storage Technologies","Jane Doe, Robert Kim","University of Technology, California",2023,"This paper explores recent developments in battery technologies for renewable energy storage, focusing on lithium-ion, solid-state, and flow batteries. It r... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-7122533</review_id>
<content>Expert difficult hot radio mission. Throw ... | Approach:
1. Task: Convert customer review from XML to 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. Transform values to match the target format specifications.
Output:... | {
"customer_review": {
"review_id": "REV-7122533",
"content": "Expert difficult hot radio mission. Throw southern he book way media particular.",
"rating": 1,
"date": "2026-01-06",
"verified_purchase": false
}
} |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Convert the following JSON to XML:
{
"order_date": "2026-01-05",
"results": [
{
"test": "Hemoglobin",
"value": 95.5,
"unit": "g/dL",
"flag": "low"
... | Approach:
1. Task: Convert lab result 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... | <order>
<order_date>2026-01-05</order_date>
<results>
<result>
<test>Hemoglobin</test>
<value>95.5</value>
<unit>g/dL</unit>
<flag>low</flag>
</result>
<result>
<test>Hemoglobin</test>
<value>52.7</value>
<unit>mg/dL</unit>
<flag>high</flag>
</result>
... |
<|im_start|>system
You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.<|im_end|>
<|im_start|>user
Output error log as XML.<|im_end|>
<|im_start|>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="... | <?xml version="1.0" encoding="UTF-8"?>
<error_log>
<entry>
<timestamp>2023-10-05T14:32:17Z</timestamp>
<error_code>404</error_code>
<message>Resource not found</message>
<file>src/controllers/userController.js</file>
<line>89</line>
<severity>error</severity>
</en... |
<|im_start|>system
You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.<|im_end|>
<|im_start|>user
Produce a TOML document for a customer review.<|im_end|>
<|im_start|>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:
date = "2026-01-04... | [customer_review]
title = "Great Product, Excellent Service"
rating = 5
reviewer_name = "Sarah J."
review_date = "2024-04-15"
content = "I was extremely satisfied with the product quality and the fast shipping. The customer service team was responsive and helpful throughout the process. Highly recommend this to anyone ... |
<|im_start|>system
You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.<|im_end|>
<|im_start|>user
Create a JSON representation of sales analytics.<|im_end|>
<|im_start|>assistant
| Approach:
1. Task: Create sales analytics 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:
{
"pe... | {
"sales_analytics": {
"period": "2024-01-01 to 2024-12-31",
"total_revenue": 1567890.50,
"average_daily_sales": 4299.70,
"top_product_category": "Electronics",
"top_performing_region": "North America",
"sales_trend": {
"monthly_growth": 8.5,
"quarterly_growth": 25.3
},
"cu... |
<|im_start|>system
You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.<|im_end|>
<|im_start|>user
Reformat the data below from JSON to CSV:
{
"article_id": "ART-8668047",
"headline": "Seamless local alliance",
"author": "Alyssa Moore",
"published": "2026-01-02T06:22:52.... | Approach:
1. Task: Convert news article 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:
article_i... | article_id,headline,author,published,section,content,tags,views,shares
"ART-8668047","Seamless local alliance","Alyssa Moore","2026-01-02T06:22:52.413807","Business","Billion up year window similar. Oil two resource next. If this tough pattern.\nRule year push international.\nReceive charge movie remember hear theory s... |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 4