---
title: "Long-form Extraction"
slug: "long-form-extraction"
updated: 2025-11-21T15:59:59Z
published: 2025-11-21T15:59:59Z
canonical: "help.hyperscience.ai/long-form-extraction"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Long-form Extraction

Hyperscience’s solution for documents that consist of longer paragraphs of text that span across multiple pages is called *Long-form Extraction*. It builds upon the Long-form Extraction model. To learn more, see [Long-form Extraction Field ID model](/v41/docs/training-a-new-field-identification-model#long-form-extraction-field-id-model).

Long-form Extraction is available for:

- Flexible Extraction
- Field ID & Field ID QA

To make the extraction of longer text possible, we implemented a new data type called “Clause.”![](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/24808428766733.png)

The Clause data type can only be added to fields, not tables, in the Layout Editor.

## Prerequisites

To use Long-form Extraction, you first need to ensure that your infrastructure, data type, and engine type are set up correctly.

### GPU trainer

A GPU trainer is required in order to use Long-form Extraction. To learn more about the technical requirements for GPUs, see [Infrastructure Requirements](/deployment/docs/infrastructure-requirements#gpu) (for Docker and Podman) or [Kubernetes Installation Overview](/deployment/docs/kubernetes-installation-requirements#gpus-for-trainers).

If you have an on-premise deployment of Hyperscience, you need to follow the steps in the "Enabling Trainers with GPUs" article for [Docker](/deployment/docs/enabling-trainers-with-gpus-in-on-premise-docker-deployments), [Podman](/deployment/docs/enabling-trainers-with-gpus-in-on-premise-podman-deployments), or [Kubernetes](/deployment/docs/enabling-trainers-with-gpus-in-on-premise-kubernetes-deployments) before using your trainer.

### Clause data type

Before using Long-form Extraction, make sure to set the data type of the field with longer text in your layout to **Clause**. Learn more in [Creating Semi-Structured Layouts](/v41/docs/creating-semi-structured-layouts).

Custom Data types also work with Clause, as long as the ML Configuration is set to *Entry - Clause*:

![](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/24808428767373.png)

Learn more about ML Configurations in [Creating Data Types with ML Configurations](/v41/docs/creating-data-types-with-ml-configurations).

### Long-form Extraction Engine type

> [!NOTE]
> Long-form Extraction Engine type
> 
> The default Field Identification models use a generic engine type that cannot extract data points from documents with unstructured text.To learn more, see [Training a New Field Identification Model](/v41/docs/training-a-new-field-identification-model).
> 
> To extract data points from Unstructured documents using a specific layout, you need to select the **Long Form Extraction** engine type for that layout before training the model.

Follow the steps below to change the engine type of your layout:

1. Go to **Library** > **Layouts** and open your layout.
2. On the **Configuration** card, click the **Edit** button (![](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/image(130).png)) under the **Engine Type** setting.
3. Select **Long Form Extraction** from the drop-down menu.
4. Click **Change Type**.

![](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/2025-03-27_22-08-35 (1)(1).gif)

1. Retrain your model after you’ve changed the engine type of the layout.

## Using Long-form Extraction

1. Annotate your documents by using the **Add another text segment** option for fields that span across multiple pages. Learn more in [Multiple bounding boxes for fields](/v41/docs/field-identification#multiple-occurrences-model).
2. Preview the transcribed values on the right-hand side of the Document Viewer.

## Long-form Extraction limits

Below is a list of the limits that apply for training a Long-form Extraction model.

- 2,000 text segments per page
- 200 pages per document
- 200,000 text segments per document
- 100,000,000 text segments total

To learn more about segments, see [Text Segmentation](/v41/docs/segmentation).