AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 2 November 2026

Can LlamaParse use a supplied definition to choose the right value?

LlamaParse returned the consignment reference CFS-CN-40821, as the field definition asked, rather than the invoice number CFS-7710. The invoice number is printed more prominently in the header and on every page.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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.

Definition overrides the prominent numberPassEvidence
What we sent

We uploaded the freight invoice to the Extract page with a schema defining one required text field whose description selects the consignment reference and excludes the invoice number.

Input 1Document (PDF)
Input PDF: three-page freight invoice with two candidate reference numbers
Open the PDF ↗
Input 2File (JSON)
Input schema: the generic field and its deciding definition
JSON
{
  "type": "object",
  "properties": {
    "reference_number": {
      "type": "string",
      "description": "The consignment reference number, the identifier tied to the physical shipment. This is NOT the invoice number, even though the invoice number appears more prominently (labelled, and repeated in the footer of every page)."
    }
  },
  "required": ["reference_number"]
}
Open the JSON file ↗
What the tool returned
Text
"reference_number": "CFS-CN-40821"

Extraction output: the selected reference number.

Copied from Output file (JSON), lines 9–11 · an excerpt

Open the whole JSON file ↗

Source excerpt · partial file · response 1

JSON
"extract_result": {
  "reference_number": "CFS-CN-40821"
},

Copied from Output file (JSON), lines 9–11 · an excerpt

Expected vs. Found
✓Expected: Return the value named by the supplied definition, not the more prominent one.Found: It returned the consignment reference on page 1 and did not return the invoice number.
Supporting proof
Proof 1Screenshot
Results screen: the extracted reference number beside the uploaded invoice
Open original ↗
Why this result

The field definition excluded the invoice number, and the returned value was the consignment reference on page 1. The repeated invoice number remained the more prominent alternative in the pages' headers and footers, so the definition controlled the answer.

Also observed in this test case

Location and confidence. The consignment reference has a page-1 citation with a bounding box and confidence of 0.9501241833995158.

Tested by Rugved Nichite · evidence dated 28 October 2026

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.

Software that produced the output
LlamaParse
Build or version
LlamaCloud web app (build v9bc3d1a1)
Plan or tier
Free plan (20,000 credits)
Surface
Web app
Set up before the run
One required field had to be named generically and defined so it excluded the more prominent candidate. The run used the Extract surface, the agentic tier, and the Free plan.
Extraction tier
agentic
Feature
Extract
Tested
28 October 2026 · Rugved Nichite

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
20 November 2026First publishedStructured Document Extraction v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/llamaparse/the-value-needs-a-supplied-definition · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-02

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.

Input 1 · Document (PDF) ↗application/pdf · 118 KB
Input 2 · File (JSON) ↗application/json · 0 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 1 KB
Proof 1 · Screenshot ↗image/png · 110 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)1bcc6c7b945956c5b6f5a87d223ed3d578a62aa2c56c5fc1e3abedb4cc4de72e
Input 2 · File (JSON)201abd57dbe65d3c60d7d50ad5898a450fbacb194515170debc9d406573317d8
Output file (JSON)aed7fa8589c7a15fe4ff35b59639fec0c7f8b008ca4b4b3118607873cee68ab3
Proof 1 · Screenshot4aade995b070db79912772357f8ac92ed88070570a1474bccdc6d55c34856c92