[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 69, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.7247ba54dfed", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "city centre", "yes"]}}}

<|document|>
[DOCUMENT]
In the city centre there is a family-friendly place called Alimentum.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}

The script extracts key-value pairs from the document according to the schema.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 69, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.dbb1479035f1", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
In the city centre there is a family-friendly place called Alimentum.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes"}

The output contains a single row as the "structure" is "flat_single_row" in the schema.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 65, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.0b4013521e0b", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "city centre", "yes"]}}}

<|document|>
[DOCUMENT]
The city centre has a family-friendly restaurant named Alimentum.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}

The output is generated based on the schema provided and the information present in the document. The document mentions the city centre having a family-friendly restaurant named Alimentum, which matches the schema's expected fields.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 65, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.76449e16f577", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
The city centre has a family-friendly restaurant named Alimentum.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes"}

The task only requires filling a single row with data from the document, so the output is a single JSON object.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 40, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.e04e69c0161e", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "city centre", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum city centre is family-friendly

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}

The output matches the requirements because it:

- Extracts only explicitly supported facts from the document
- Uses exact columns and order as specified in the schema
- Outputs JSONL with no commentary or extra characters
- Uses deterministic processing for identical input
- Trims whitespace in strings and preserves original case and spacing
- Keeps IDs/codes as strings and dates in original format
- Handles booleans, integers, and numbers as specified
- Treats missing values as specified
- Processes key-value tables as specified


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 40, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.3eb7ab1c46b5", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum city centre is family-friendly

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes"}


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 43, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.d3794726214a", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "city centre", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum is a family-friendly city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}

The output is deterministic and meets all the requirements specified in the policy and task.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 43, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.1d95bbd2e00a", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum is a family-friendly city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes"}

The output is a single row as per the schema structure of "flat_single_row". The values are extracted directly from the document as specified.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 73, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.e068c7d328fa", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "city centre", "yes"]}}}

<|document|>
[DOCUMENT]
There is a family-friendly restaurant named Alimentum in the city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}

The output consists of three separate JSON objects corresponding to each row in the table, with the "slot" and "value" keys, which match the schema.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 73, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.995d7808c798", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
There is a family-friendly restaurant named Alimentum in the city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes"}

The output follows the provided policy and schema.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 77, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.e3076e7c2463", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
Alimentum is family oriented and located near Burger King in the city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is a JSON Lines (JSONL) file with one JSON object per row, following the schema provided. The values are extracted directly from the document without any inferences or assumptions.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 77, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.3e8dd37bdba9", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum is family oriented and located near Burger King in the city centre.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

The document does not mention family oriented, so I output an empty string for that field.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 90, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.59d8f9f56131", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
The Alimentum is a family-friendly restaurant located in the city centre near Burger King.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is a JSONL representation of the table under the given schema, where each line represents a row in the table, and the keys match the schema exactly in the same order.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 90, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.988ce42b3b0c", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
The Alimentum is a family-friendly restaurant located in the city centre near Burger King.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

(Note: the output is a single JSON object per row as per the requirements, with keys exactly as in the schema and in the same order)


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 91, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.fa1fe8bd395d", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
Located in the city centre near Burger King, the Alimentum is a family-friendly restaurant.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is in the required JSONL format, with keys exactly as in the schema and in the same order. Each cell has an empty string when the value is not explicitly present in the document.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 91, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.f29800607a56", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
Located in the city centre near Burger King, the Alimentum is a family-friendly restaurant.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

(The document does not provide information about the exact area near Burger King, or the exact name of the city, but we can still fill the table with the given information. I assume "city centre" as the area and "Alimentum" as the name, based on the given text.)


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 75, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.92e9a2e47d60", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
Alimentum, located near Burger King in the city centre, is family-friendly.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is in the required format, with each JSON object per row, exact column names, and no comments or markdown. The schema fields are matched with the corresponding values from the document, and empty strings are used for missing values.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 75, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.fb4a43b892ca", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum, located near Burger King in the city centre, is family-friendly.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

I will process the document to extract the information according to the schema.

The name of the restaurant is "Alimentum".
The area is "city centre".
The restaurant is "family-friendly" as indicated by the phrase "family-friendly" in the document.
The restaurant is near "Burger King".

Here is the extracted information in the required JSON format:

{"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 69, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.72833b567a5b", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
Located Burger King in the city centre, Alimentum is family-friendly.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is based on the provided schema and document.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 69, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.cbf10a584282", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
Located Burger King in the city centre, Alimentum is family-friendly.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

I've filled the table under the provided schema using facts from the document.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 77, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.538bc58cda50", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly", "near"], "value": ["Alimentum", "city centre", "yes", "Burger King"]}}}

<|document|>
[DOCUMENT]
Alimentum is family-friendly and located in the city centre near Burger King.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "city centre"}
{"slot": "familyFriendly", "value": "yes"}
{"slot": "near", "value": "Burger King"}

The output is in JSONL format, with keys exactly as in the schema, and in the same order. Each line is a valid JSON object.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 77, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.862403e89552", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}, {"name": "near", "type": "string", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum is family-friendly and located in the city centre near Burger King.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "city centre", "familyfriendly": "yes", "near": "Burger King"}

(I have output a single row as the structure of the schema is "flat_single_row")


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 71, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.22c23ecfb8c2", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "riverside", "no"]}}}

<|document|>
[DOCUMENT]
Alimentum looks like a location where people or families aren't allowed

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "riverside"}
{"slot": "familyFriendly", "value": "no"}

The task instructions do not ask for a summary or an explanation of the code but rather only the output in the specified format.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 71, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.084f681de859", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum looks like a location where people or families aren't allowed

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "riverside", "familyfriendly": "no"}

The document mentions "Alimentum" as a location where people or families aren't allowed, implying that it is not family-friendly.

Additionally, the name "Alimentum" and the word "riverside" as an area are extracted from the document.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 55, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.4ee696c6c05e", "structure": "kv_multi", "description": "Schema induced from the gold table.", "fields": [{"name": "slot", "type": "string", "required": true}, {"name": "value", "type": "string", "required": true}], "constraints": {"enums": {"slot": ["name", "area", "familyFriendly"], "value": ["Alimentum", "riverside", "no"]}}}

<|document|>
[DOCUMENT]
Alimentum isn't family-friendly but it is in riverside.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant]
{"slot": "name", "value": "Alimentum"}
{"slot": "area", "value": "riverside"}
{"slot": "familyFriendly", "value": "no"}

The output is generated based on the provided schema and document. The document explicitly states "Alimentum isn't family-friendly but it is in riverside." which implies the following table structure:

- "name": Alimentum
- "area": riverside
- "familyFriendly": no

This matches the schema exactly, with no missing values or additional columns.


[System] You convert documents into tabular data strictly under a provided JSON schema. Output ONLY JSON Lines (one JSON object per row), with EXACT columns and order as the schema, and no commentary.

[User]
<|policy|>
[POLICY]
- Extract only facts explicitly supported by the document. No guessing, no background knowledge, no synonyms.
- Never invent rows or columns. If a value is not present, output an empty string for that cell.
- Output exactly the columns listed in [SCHEMA]. The key order in each JSON object MUST match the schema order.
- Do not add headers, comments, explanations, or markdown. Emit ONLY raw JSONL (one JSON object per line).
- Output must be deterministic for identical input.
- Trim leading/trailing whitespace in strings; preserve internal spacing and case from the document.
- IDs/codes stay strings (preserve leading zeros). Do not convert units or reformat currencies.
- Booleans accept tokens ⊆ {true,false,yes,no,1,0,t,f} (case-insensitive). Keep the surface form unless the schema requires normalization.
- Integers: ^[+-]?\d+$ (after trim). Numbers: plain JSON numbers if unambiguous; otherwise keep as strings.
- Dates: prefer ISO-like YYYY, YYYY-MM, or YYYY-MM-DD if explicitly present; otherwise keep as strings.
- Treat as missing (case-insensitive, after trim): "", -, —, –, N/A, NA, None, Null, Unknown, TBD, and the na_token from [METADATA]. For missing values, emit empty string "".
- For pivot-like tables, emit a single row per entity with all columns populated when available.
- For key–value (slot/value) tables, emit one row per pair with exactly the two columns from the schema.
- No trailing commas. Ensure every line is valid JSON. Do not wrap rows in an array. No code fences.

<|metadata|>
[METADATA]
{"language": "en", "script": "auto", "direction": "auto", "source_modality": "plain_text", "na_token": "", "document_char_len": 55, "table_count": "auto", "structure_candidates": ["kv_single", "kv_multi", "flat_single_row", "row_grouped"], "table_hints": {"header_rows_max": 3, "header_cols_max": 2, "row_header_possible": true, "col_header_possible": true, "ragged_rows_possible": false, "multiple_tables_possible": true}, "locale": {"numeric": "auto", "decimal_separators": [".", ","], "thousand_separators": [",", ".", " "], "negative_patterns": ["-x", "(x)"], "percent_symbol": "%", "permille_symbol": "‰"}, "parsing_hints": {"kv_markers": [":", "—", "–", "=", "→"], "list_markers": ["- ", "* ", "• ", "•\t", "▪ "], "section_markers": ["###", "##", "--", "__", "**", ":"]}, "missing_tokens": ["", "-", "—", "–", "N/A", "NA", "None", "Null", "Unknown", "TBD"]}

<|schema|>
[SCHEMA]
{"schema_id": "gold.23fd465cd782", "structure": "flat_single_row", "description": "Schema induced from the gold table.", "fields": [{"name": "name", "type": "string", "required": true}, {"name": "area", "type": "string", "required": true}, {"name": "familyfriendly", "type": "boolean", "required": true}]}

<|document|>
[DOCUMENT]
Alimentum isn't family-friendly but it is in riverside.

<|output_format|>
[OUTPUT_FORMAT]
Emit ONLY JSON Lines (JSONL), one JSON object per row, with keys exactly as in [SCHEMA] and in the same order. Do NOT wrap in an array. No comments or markdown.

<|task|>
[TASK]
Fill the table under the given [SCHEMA] using facts from [DOCUMENT]. If a value is not explicitly present, output an empty string for that cell. Ensure every line is valid JSON.

[Assistant] {"name": "Alimentum", "area": "riverside", "familyfriendly": "no"}