[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": 72, "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.e1d43f70ac2b", "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", "yes"]}}}

<|document|>
[DOCUMENT]
There is a family-friendly venue in the riverside area 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output matches the [OUTPUT_FORMAT] requirement, which is to emit JSON Lines (one JSON object per row), with keys exactly as in [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": 72, "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.1bb32df77e81", "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 venue in the riverside area 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": "riverside", "familyfriendly": "yes"}

The decision was made based on the information given in the document: "There is a family-friendly venue in the riverside area called Alimentum." The keywords "family-friendly", "riverside", and "Alimentum" were used to populate the table according to the schema provided.


[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": 66, "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.0c4dc53073ae", "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", "yes"]}}}

<|document|>
[DOCUMENT]
At the riverside there is a friendly family 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is deterministic, as required.


[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": 66, "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.879b24360285", "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]
At the riverside there is a friendly family 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": "riverside", "familyfriendly": "yes"}

(Note: The task asked for a single JSON object per line. Since the schema has three columns, and there's only one fact in the document that can be extracted, 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": 85, "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.bab148023b80", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Located in riverside area, Alimentum restaurant is a place to bring the whole family.

<|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": "yes"}

The output follows the provided schema and meets all requirements.


[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": 85, "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.6c060dfcba18", "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]
Located in riverside area, Alimentum restaurant is a place to bring the whole family.

<|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": "yes"}

The word "whole" is missing from the output, but it can be interpreted as "yes" in this context, based on the sentence "a place to bring the whole family", which suggests the restaurant is family-friendly. However, since the schema requires a boolean value, and the word "whole" can also mean not a part, it might be more accurate to output "no".


[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.7c4ed858a840", "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", "yes"]}}}

<|document|>
[DOCUMENT]
There is a riverside restaurant called Alimentum which is child 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is in the correct format, with exactly the columns listed in the schema and in the same order. Each row represents a separate key-value pair 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": 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.212d60d24c51", "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 riverside restaurant called Alimentum which is child 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": "riverside", "familyfriendly": "yes"}

The output is a single row with all columns populated because the document describes a single entity (restaurant) with all the required information.


[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": 59, "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.11b1735f3674", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum can be found in riverside and 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is in the required JSONL format with the exact columns and order specified 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": 59, "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.96800336021a", "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 can be found in riverside and 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": "riverside", "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": 61, "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.6023ede3c948", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Being beside the river, Alimentum is a family friendly place.

<|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": "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": 61, "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.2da3306475bf", "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]
Being beside the river, Alimentum is a family friendly place.

<|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": "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": 63, "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.221751442866", "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", "yes"]}}}

<|document|>
[DOCUMENT]
A family friendly place near the riverside is 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is generated by parsing the document and matching the schema. The document states that "Alimentum" is a family-friendly place near the "riverside", which matches the schema. The "familyFriendly" slot is explicitly mentioned as "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": 63, "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.4b3131c4a177", "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]
A family friendly place near the riverside is 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": "riverside", "familyfriendly": "yes"}

The word "family friendly" directly indicates that the place is suitable for families, which can be interpreted as "yes" for the "familyfriendly" 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": 54, "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.6bde6eb7fd67", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Visit Alimentum by the riverside, it is kids 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is determined by the provided schema and document. The schema specifies that the table structure is "kv_multi" and the fields are "slot" and "value". The document contains two mentions of the word "Alimentum" and "riverside", which are used to populate the "slot" and "area" values. Additionally, the phrase "kids friendly" is used to populate the "familyFriendly" value.


[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": 54, "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.318425688028", "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]
Visit Alimentum by the riverside, it is kids 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": "riverside", "familyfriendly": "yes"}

The JSON output follows the specified requirements, including the exact column order and formatting as specified 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": 64, "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.c6ed01ee93ec", "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", "yes"]}}}

<|document|>
[DOCUMENT]
For a riverside, child friendly environment visit the 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is deterministic for the given input, and the key order in each JSON object matches the schema 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": 64, "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.2277a190882a", "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]
For a riverside, child friendly environment visit the 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": "riverside", "familyfriendly": "yes"}

The provided document does not contain enough information to fill in the "area" and "familyfriendly" columns with certainty. The task requires extracting facts explicitly supported by the document, and in this case, the document only mentions the name of the location.


[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": 62, "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.48c4d12d000b", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum is located near the riverside. It is child 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output matches the requirements of the task and the policy provided.

1. The output is in JSONL format, one JSON object per line.
2. The keys in each JSON object match the order and names in the provided schema.
3. The schema does not allow missing values, so empty strings are used instead.
4. The values for "name", "area", and "familyFriendly" are extracted directly from the document.
5. The values are strings, as per the schema, and trimmed of leading/trailing whitespace.
6. The output is deterministic and does not require background knowledge or guessing.
7. The values are in the same format as they appear in the document, following the policy's requirements for date, integer, and boolean formatting.


[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": 62, "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.d6bba8ae2abd", "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 located near the riverside. It is child 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": "riverside", "familyfriendly": "yes"}

The document explicitly states that "It is child friendly", which can be interpreted as "yes" for the "familyfriendly" 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": 50, "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.1a1add8cffb9", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum in the riverside area is child 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is in the format of JSONL (JSON Lines), one JSON object per row, with keys exactly as in the provided [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": 50, "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.2b510dc469da", "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 in the riverside area is child 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": "riverside", "familyfriendly": "yes"}

(Note: This output is determined based on the provided schema and document. The document explicitly states "Alimentum in the riverside area is child friendly", which can be broken down as follows:

- name: Alimentum
- area: riverside
- familyfriendly: "child friendly" can be interpreted as "yes" in the context of the schema, given that "yes" is an accepted value for the boolean field "familyfriendly".


[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": 48, "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.e2562bb75a8f", "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", "yes"]}}}

<|document|>
[DOCUMENT]
Alimentum, on the riverside, 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": "riverside"}
{"slot": "familyFriendly", "value": "yes"}

The output is generated based on the provided JSON schema and document. The document contains a name, an area, and a family-friendliness value, which match the slot names 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": 48, "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.193e08ae27c8", "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, on the riverside, 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": "riverside", "familyfriendly": "yes"}

The JSONL output only contains one row because the document describes only one restaurant, Alimentum.