messages listlengths 3 3 | metadata dict |
|---|---|
[
{
"content": "You are an expert in CSV format. Generate syntactically perfect CSV. Output only valid CSV with no additional text, comments, or markdown fences. Include a header row. Use commas as delimiters. Quote fields that contain commas, newlines, or double quotes.",
"role": "system"
},
{
"conte... | {
"complexity": "medium",
"estimated_tokens": 189,
"format": "csv",
"schema": "financial_report",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 195,
"format": "json",
"schema": "sales_analytics",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the... | {
"complexity": "complex",
"estimated_tokens": 246,
"format": "toml",
"schema": "error_log",
"type": "conversion"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "medium",
"estimated_tokens": 193,
"format": "yaml",
"schema": "social_media_post",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "complex",
"estimated_tokens": 218,
"format": "json",
"schema": "news_article",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "simple",
"estimated_tokens": 145,
"format": "yaml",
"schema": "clinical_note",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "complex",
"estimated_tokens": 133,
"format": "toml",
"schema": "product_listing",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "complex",
"estimated_tokens": 172,
"format": "json",
"schema": "customer_review",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "simple",
"estimated_tokens": 157,
"format": "toml",
"schema": "research_paper",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "complex",
"estimated_tokens": 193,
"format": "json",
"schema": "experiment_result",
"type": "conversion"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "medium",
"estimated_tokens": 187,
"format": "toml",
"schema": "lab_result",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the... | {
"complexity": "medium",
"estimated_tokens": 165,
"format": "toml",
"schema": "contract",
"type": "conversion"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "complex",
"estimated_tokens": 248,
"format": "json",
"schema": "experiment_result",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "complex",
"estimated_tokens": 194,
"format": "yaml",
"schema": "social_media_post",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the... | {
"complexity": "medium",
"estimated_tokens": 161,
"format": "toml",
"schema": "social_media_post",
"type": "conversion"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "medium",
"estimated_tokens": 223,
"format": "toml",
"schema": "research_paper",
"type": "generation"
} |
[
{
"content": "You are a specialist in CSV structures. Study the data format, then create valid CSV. Output only valid CSV with no additional text, comments, or markdown fences. Include a header row. Use commas as delimiters. Quote fields that contain commas, newlines, or double quotes.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 162,
"format": "csv",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in CSV format. Analyze the data structure and generate syntactically perfect CSV. Output only valid CSV with no additional text, comments, or markdown fences. Include a header row. Use commas as delimiters. Quote fields that contain commas, newlines, or double quotes.",
"role... | {
"complexity": "medium",
"estimated_tokens": 150,
"format": "csv",
"schema": "product_listing",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "simple",
"estimated_tokens": 127,
"format": "json",
"schema": "customer_review",
"type": "conversion"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 182,
"format": "json",
"schema": "customer_review",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 171,
"format": "xml",
"schema": "contract",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 221,
"format": "xml",
"schema": "error_log",
"type": "conversion"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "complex",
"estimated_tokens": 200,
"format": "toml",
"schema": "news_article",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Analyze the data structure and generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the... | {
"complexity": "medium",
"estimated_tokens": 159,
"format": "toml",
"schema": "financial_report",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 250,
"format": "xml",
"schema": "api_specification",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 165,
"format": "xml",
"schema": "contract",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 201,
"format": "json",
"schema": "social_media_post",
"type": "conversion"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "complex",
"estimated_tokens": 182,
"format": "yaml",
"schema": "course_syllabus",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 221,
"format": "xml",
"schema": "sales_analytics",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "complex",
"estimated_tokens": 242,
"format": "yaml",
"schema": "student_assessment",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 166,
"format": "xml",
"schema": "contract",
"type": "conversion"
} |
[
{
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
... | {
"complexity": "medium",
"estimated_tokens": 159,
"format": "yaml",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 218,
"format": "xml",
"schema": "error_log",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 180,
"format": "xml",
"schema": "clinical_note",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "medium",
"estimated_tokens": 135,
"format": "toml",
"schema": "product_listing",
"type": "generation"
} |
[
{
"content": "You are an expert in CSV format. Generate syntactically perfect CSV. Output only valid CSV with no additional text, comments, or markdown fences. Include a header row. Use commas as delimiters. Quote fields that contain commas, newlines, or double quotes.",
"role": "system"
},
{
"conte... | {
"complexity": "complex",
"estimated_tokens": 196,
"format": "csv",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 216,
"format": "json",
"schema": "news_article",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
... | {
"complexity": "medium",
"estimated_tokens": 182,
"format": "yaml",
"schema": "social_media_post",
"type": "conversion"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 191,
"format": "json",
"schema": "experiment_result",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 186,
"format": "json",
"schema": "error_log",
"type": "conversion"
} |
[
{
"content": "You are a specialist in CSV structures. Create valid CSV. Output only valid CSV with no additional text, comments, or markdown fences. Include a header row. Use commas as delimiters. Quote fields that contain commas, newlines, or double quotes.",
"role": "system"
},
{
"content": "Outpu... | {
"complexity": "complex",
"estimated_tokens": 251,
"format": "csv",
"schema": "prescription",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 182,
"format": "xml",
"schema": "product_listing",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 179,
"format": "xml",
"schema": "clinical_note",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 222,
"format": "xml",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "medium",
"estimated_tokens": 158,
"format": "yaml",
"schema": "lab_result",
"type": "generation"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "complex",
"estimated_tokens": 170,
"format": "json",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in YAML format. Analyze the data structure and generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
... | {
"complexity": "simple",
"estimated_tokens": 168,
"format": "yaml",
"schema": "error_log",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 162,
"format": "xml",
"schema": "financial_report",
"type": "generation"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "medium",
"estimated_tokens": 231,
"format": "xml",
"schema": "api_specification",
"type": "conversion"
} |
[
{
"content": "You are an expert in XML format. Generate syntactically perfect XML. Output only valid XML with no additional text, comments, or markdown fences. Include proper opening and closing tags for every element. Use consistent indentation for nested elements.",
"role": "system"
},
{
"content"... | {
"complexity": "complex",
"estimated_tokens": 209,
"format": "xml",
"schema": "customer_review",
"type": "conversion"
} |
[
{
"content": "You are an expert in JSON format. Generate syntactically perfect JSON. Output only valid JSON with no additional text, comments, or markdown fences. Use proper indentation with consistent nesting. Ensure all strings are double-quoted and arrays/objects are properly closed.",
"role": "system"
... | {
"complexity": "medium",
"estimated_tokens": 202,
"format": "json",
"schema": "social_media_post",
"type": "generation"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "medium",
"estimated_tokens": 224,
"format": "toml",
"schema": "research_paper",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "medium",
"estimated_tokens": 120,
"format": "yaml",
"schema": "prescription",
"type": "conversion"
} |
[
{
"content": "You are an expert in TOML format. Generate syntactically perfect TOML. Always use standard TOML section headers like [section] and [[array_of_tables]]. Never use inline tables such as {key = value} or inline arrays. Place each key-value pair on its own line under the appropriate section header.",
... | {
"complexity": "medium",
"estimated_tokens": 160,
"format": "toml",
"schema": "error_log",
"type": "generation"
} |
[
{
"content": "You are an expert in YAML format. Generate syntactically perfect YAML. Output only valid YAML with no additional text, comments, or markdown fences. Use consistent indentation (2 spaces). Use block style for nested structures, not flow style like {key: value}.",
"role": "system"
},
{
"... | {
"complexity": "complex",
"estimated_tokens": 170,
"format": "yaml",
"schema": "api_specification",
"type": "conversion"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.