Tool in benchmark · Version 1

Nanonets in Structured Document Extraction

Scenario-level performance from current published Results.

6 scenarios with published Results · 19 scenarios in the benchmark

How Nanonets 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 · 1 with published Results
ScenarioPublished outcomesTest coverageResult
The value must be derived
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets derived the requested value from the two present inputs and returned 81 for total_fuel_cost. The two operand rows carried source-link icons in the screenshot and the total row did not, matching the JSON output and showing the value as a computed field.

1/1 assessed1/1 gradablePublished test setView Result →
The field is absentNo published result
The same field across layoutsNo published result
The value is directly availableNo published result
The value needs a supplied definitionNo published result
Nested & Repeated Fields4 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
The set continues across a page break
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets kept one array across the page break. The output has ten objects in one top-level array, with no second array and no repeated member at the boundary. The invoice shows items 1-6 on page 1 and 7-10 on page 2, and the result screen shows the same single table numbered 1 to 10.

1/1 assessed1/1 gradablePublished test setView Result →
A repeated set of recordsNo published result
The set contains a non-recordNo published result
The set is legitimately emptyNo published result
OCR2 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
A document mixing digital and scanned pages
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets handled the mixed digital-and-scanned document in this test. It returned the five requested values, including the two that appear only in the scanned page image, and kept the digital-page values unchanged. The JSON output itself does not show per-value page provenance.

1/1 assessed1/1 gradablePublished test setView Result →
A cleanly scanned documentNo published result
Querying3 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
Filter records across documents
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets returned the matching documents for the tested cross-document filter. It produced the two receipts above $150 and left out the one below that threshold. The screenshot also shows a Data Extraction step over three files before the final JSON answer.

1/1 assessed1/1 gradablePublished test setView Result →
Aggregate across documentsNo published result
The answer was never in the schemaNo published result
Review and Correction3 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
Corrected data goes downstream
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets passes this scenario. In the tested case, the corrected receipt number appears in the product’s delivery path: the result grid shows RHS-99999, the Download menu is open on that grid, and the exported JSON carries RHS-99999 with the other receipt values.

1/1 assessed1/1 gradablePublished test setView Result →
Correct a field valueNo published result
Repair a recordNo published result
Source Grounding2 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
Trace a value to its location
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Nanonets traced the returned subtotal to page 2, where GBP 6,103.00 is highlighted in the totals block. The exported page number was 2, and the preview highlight sat on the returned value rather than the neighboring totals.

1/1 assessed1/1 gradablePublished test setView Result →
The field is absentNo published result
Training1 scenario · 0 with published Results
ScenarioPublished outcomesTest coverageResult
A field the tool can only get right from examplesNo published result

Reading these Results

Published evidence and test coverage answer different questions.

Publication availability

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.

Test coverage

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.

Scenario scope

Inventory is not testing progress

The 19 scenarios describe this benchmark’s scope. They are not an assumed applicability or test-coverage denominator for Nanonets.

Nanonets in Structured Document Extraction | AI Demos