Extraction Model Chaining

Extract data from detected crops.

Use Crop to automatically extract document data, meaning that several different extractions can be made for a single image.

Note: Crop Models also work on multi-page files, with potentially multiple crop items for each page. However each crop item is limited to an area on a single page. If you need a single extraction result covering multiple pages, take a look at Split Models instead.

Extraction Set Up

At Model Creation

When creating your Crop model, you'll be adding document classes in the creation window.

For each document class, you can link one of your Extraction Models for chaining. The Extraction Model must exist prior to the Crop Model creation.

Use the search field to filter available extraction models.

After Model Creation

This works exactly like when creating at model creation.

Simply go to your Crop Model's "Utility Configuration" page and adjust as needed.

You can add new classes, remove classes, and change Extraction Models.

Selectively Extracting

If a detected class has no linked Extraction Model, no extraction runs for that crop.

This allows selectively extracting some parts while ignoring others.

Let's say your users upload images of their trip documents on their hotel table, typically but not limited to: plane tickets, travel receipts, driver license, and passport.

You need only the passports.

In your Crop configuration, add a passport class and an other class, and only link an extraction model to the passport class.

All crop items will get classified, but only those linked to an Extraction Model will have extraction results.

Add an other class in addition to classes of interest to you, unless all potential document types are known in advance.

Token Usage With Chaining

You only consume tokens once, there is no double charge when chaining to an Extraction model.

The possible credit consumption scenarios are as follows:

• extraction model not chained ⇒ token usage of initial model (Split, Crop, Classification)
• extraction model chained ⇒ token usage of the configured extraction model, including any activated optional features.

In other words, the initial model is provided at no additional cost to you if it triggers additional processing using an Extraction model.

All token consumption is per page as is standard for our models.

Access Extraction Results

When an Extraction Model is linked, each detected crop item with that class contains an Extraction Response object.

That object is the same as the response returned by a standalone Extraction request.

Because Crop works at object level, several crop items on the same page can each contain their own extraction result.

Check Crop Result for details on accessing crop items and their extraction responses.