Reducto in Structured Document Extraction
Scenario-level performance from current published Results.
11 of 20 scenarios published
Where Reducto failed
3 of 11 graded scenarios. Open a Result to see the conversation and the evidence.
The answer was never in the schema
Reducto gives no way to ask a question about a document, so it cannot say whether an answer came from the extracted data or the document itself. After one Parse request the technician printed on the receipt appeared among the parsed blocks; after one Extract request only the four schema fields came back.
View Result →Corrected data goes downstream
Reducto's JSON export of the job still carried the original receipt number, RHS-70234, after an attempt to change it to RHS-99999. Studio offered no way to save a replacement value, and the delivered record carried the original extraction.
View Result →Repair a record
Reducto could not repair the extracted set: its Studio results table has no add-row or delete-row controls. Reading the set back still showed the original three items: Site fencing remained and the Concrete mixer was never added.
View Result →How Reducto performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Field Extraction3 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto did not invent a value for a field the receipt does not contain. The receipt contains no loyalty, membership, or account reference, and the run returned a real null for the missing field with no citation, while the control field came back correct and cited. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The value must be derived | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto calculated a fuel cost of £81.00 from the invoice's 450 miles and £0.18 per mile. The requested total was not printed anywhere in the document. | 1/1 assessed1/1 gradablePublished test set | View 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 same field across layouts | No published result | ||
| The value is directly available | No published result | ||
Nested & Repeated Fields1 pass3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A repeated set of records | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto returned all three line items from the invoice's goods table, with all fifteen values matching the table and each value cited from its own item's row. It did not return the Subtotal, VAT or Total due rows as items. | 1/1 assessed1/1 gradablePublished test set | View 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 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A cleanly scanned document | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto read the clean scan without changing the values extracted from the digital original. Both versions returned all 20 requested values, preserving currency formatting and hire-period punctuation. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| A document mixing digital and scanned pages | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto extracted all five requested values in one call from an invoice mixing digital and scanned pages. The two values exclusive to the scanned page were returned accurately, and the digital-page values were preserved. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Querying1 fail2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The answer was never in the schema | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedReducto gives no way to ask a question about a document, so it cannot say whether an answer came from the extracted data or the document itself. After one Parse request the technician printed on the receipt appeared among the parsed blocks; after one Extract request only the four schema fields came back. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Aggregate across documents | No published result | ||
| Filter records across documents | No published result | ||
Review and Correction2 fail1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Corrected data goes downstream | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedReducto's JSON export of the job still carried the original receipt number, RHS-70234, after an attempt to change it to RHS-99999. Studio offered no way to save a replacement value, and the delivered record carried the original extraction. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Repair a record | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedReducto could not repair the extracted set: its Studio results table has no add-row or delete-row controls. Reading the set back still showed the original three items: Site fencing remained and the Concrete mixer was never added. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Correct a field value | No published result | ||
Source Grounding2 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto did not invent a value for a field the receipt does not contain. The receipt contains no loyalty, membership, or account reference, and the run returned a real null for the missing field with no citation, while the control field came back correct and cited. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Trace a value to its location | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedReducto gave a precise source location for the extracted value. It returned the £6,103.00 subtotal with a citation to the amount itself on page 2. | 1/1 assessed1/1 gradablePublished test set | View 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.