> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/split-models/extraction-model-chaining.md).
# Extraction Model Chaining
Use Split ranges to automatically extract document data, allowing for several different extractions on a multi-page file.
Note: Split Models also work on single-page files, in this case the range will always be exactly one page. If you need multiple extraction results on the same page, take a look at [Crop Models](/crop-models/crop.md) instead.
## Extraction Set Up
### At Model Creation
When creating your Split model, you'll be adding document classes in the creation window.
For each document class, you can set one of your [Extraction Models](/extraction-models/extraction-models-overview.md) for chaining. The Extraction Model must exist prior to the Split 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 Split 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 sections of the file while ignoring others.
Let's say you receive large multi-page PDFs from your users, where each PDF is a bundle of different scanned documents: plane tickets, travel receipts, driver license, and passport.
You need only the passports.
In your Split configuration, add a `passport` class and an `other` class, and only link an extraction model to the `passport` class.
All split ranges will get classified, but only those linked to an Extraction Model will have extraction results.
{% hint style="info" icon="lightbulb" %}
Always add an `other` class in addition to classes of interest to you, unless all potential document types are known in advance.
{% endhint %}
#### Removing Unused Pages
It's also possible to remove pages that are never used in the Extraction. For example to remove terms and conditions from invoices, set up the classes `terms_and_conditions_page` and `invoice_page` , and only link an Extraction Model to the `invoice_page` class.
## Access Extraction Results
When an Extraction model is linked, each Split Range with the detected class will contain an Extraction Response object, which is identical when making an Extraction request for a single document.
Check the [Split Result](/split-models/sdk-integration/split-result.md) section for more details.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.mindee.com/split-models/extraction-model-chaining.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.