Reducto in Structured Document Extraction
Scenario-level performance from current published Results.
1 of 20 scenarios published
Reducto passed every graded scenario it has a published Result for.
How Reducto performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Field Extraction1 pass4 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The value needs a supplied definition | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto followed the supplied definition when two references could fit the field name. It returned the consignment reference, not the more prominent invoice number. | 1/1 assessed1/1 gradablePublished test set | View 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 | ||
Nested & Repeated Fields4 no Result yet
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 no Result yet
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 no Result yet
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 no Result yet
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 no Result yet
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 no Result yet
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.
Out of 19 scenarios
The summary counts each of the 19 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Reducto was tested on it.