Does LlamaParse handle an absent field without inventing a value?
LlamaParse passed this absent-field case by leaving the missing loyalty field empty and ungrounded. The receipt has no loyalty wording, the extractor returned an empty value for that field, and the job record gave that field no citation metadata while the present receipt number had a citation.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Absent field returns an honest nullPassEvidence
{ "type": "object", "properties": { "receipt_number": { "type": "string", "description": "The receipt's identifying number, labelled 'RECEIPT NO'" }, "loyalty_membership_number": { "type": "string", "description": "The customer's loyalty program membership number, if the document mentions one." } }, "required": ["receipt_number", "loyalty_membership_number"] }
"extract_result": { "receipt_number": "RHS-70234", "loyalty_membership_number": "" },
Job record: empty field and citation contrast
Copied from Output file (JSON), lines 9–12
Open the JSON file ↗"receipt_number": { "citation": [ { "page": 1, "matching_text": "RHS-70234", "bounding_boxes": [ { "x": 366.623660902977, "y": 182.13455400466918, "w": 40.38487688541412, "h": 7.228088979721069 } ], "page_dimensions": { "width": 594.96, "height": 841.92 } } ], "confidence": 0.9012444791392149, "extraction_confidence": 0.9012444791392149 },
Copied from Output file (JSON), lines 16–37
"loyalty_membership_number": { "confidence": 0.6445815778174913, "extraction_confidence": 0.6445815778174913 }
Copied from Output file (JSON), lines 38–41
"status": "COMPLETED", "error_message": null,
Copied from Output file (JSON), lines 7–8
| ✓ | Expected: Return an honest null for the absent field, with no invented value or grounding attached to it.Found: The product returned an empty value for the absent field and gave that field no citation metadata. |
The test asked for a required loyalty number that the receipt does not mention. The product returned an empty value for it and gave that field no citation metadata, while the receipt number had a citation.
Empty value. The missing field is returned as an empty string, not a filled-in value.
Confidence flag. The blank field is flagged below the 90% threshold and shown in amber.
Grounding state. The job record's top-level grounded_items is null for this run.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Field Extraction → | |
| Capability | Source Grounding → | |
| Scenario | The field is absent → | |
| Tool | LlamaParse → |
Global scenario definition → · Global capability definition: Field Extraction → · Global capability definition: Source Grounding → · LlamaParse product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.