LlamaParse in Structured Document Extraction
Scenario-level performance from current published Results.
No published Results are available for LlamaParse in this benchmark. · 19 scenarios in the benchmark
Publication availability does not describe testing status.
How LlamaParse performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result; counts are not combined into an overall score.
Field Extraction5 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | No published result | ||
| The same field across layouts | No published result | ||
| The value is directly available | No published result | ||
| The value must be derived | No published result | ||
| The value needs a supplied definition | No published result | ||
Nested & Repeated Fields4 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A repeated set of records | No published result | ||
| The set contains a non-record | No published result | ||
| The set continues across a page break | No published result | ||
| The set is legitimately empty | No published result | ||
OCR2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A cleanly scanned document | No published result | ||
| A document mixing digital and scanned pages | No published result | ||
Querying3 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Aggregate across documents | No published result | ||
| Filter records across documents | No published result | ||
| The answer was never in the schema | No published result | ||
Review and Correction3 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Correct a field value | No published result | ||
| Corrected data goes downstream | No published result | ||
| Repair a record | No published result | ||
Source Grounding2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | No published result | ||
| Trace a value to its location | No published result | ||
Training1 scenario · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A field the tool can only get right from examples | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Inventory is not testing progress
The 19 scenarios describe this benchmark’s scope. They are not an assumed applicability or test-coverage denominator for LlamaParse.