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

# Process unstructured documents in Advanced Designer

> Use Advanced Designer NLP activities — Segmentation, NER, Address Parsing, Deep Learning for NLP — to extract data from contracts, emails, and freeform text.

Skills for processing [unstructured documents](/vantage/documentation/advanced-designer/use-cases/extracting-from-docs#unstructured-documents) can only be built in Advanced Designer; the cloud-based [Skill Designer](/vantage/documentation/skill-designer/skill-designer) does not support these scenarios. They use four core NLP activities to identify entities, segment text, and extract fields from freeform content like contracts, letters, and emails:

* [Segmentation activity](/vantage/documentation/advanced-designer/activities/segmentation/segmentation-activity)
* [Deep Learning for NLP activity](/vantage/documentation/advanced-designer/activities/deep-learning-nlp)
* [Named Entities (NER) activity](/vantage/documentation/advanced-designer/activities/ner)
* [Address Parsing activity](/vantage/documentation/advanced-designer/activities/address-parsing)

<Note>
  Each of these activities supports a limited set of languages. See the activity's reference page for the language list.
</Note>

## Pick a scenario

| Scenario                                         | When to use                                                       | Key activities                          |
| :----------------------------------------------- | :---------------------------------------------------------------- | :-------------------------------------- |
| Pre-trained named entities (whole document)      | Entities can appear anywhere — minimal configuration needed       | NER (+ Address Parsing)                 |
| Pre-trained named entities (specific paragraphs) | The entity always sits in a known paragraph                       | Segmentation + NER (or Address Parsing) |
| Custom named entities (Deep Learning for NLP)    | Pre-trained can't disambiguate, or your entity type isn't covered | Segmentation + Deep Learning for NLP    |

Each scenario below shares a common pattern; only the activities you add to the processing flow differ.

## Common workflow

<Steps>
  <Step title="Create a Document skill">
    Open Advanced Designer and click **Create Document Skill** on the start page.
  </Step>

  <Step title="Upload documents">
    On the **Documents** tab, upload the documents you'll use to set up the skill.
  </Step>

  <Step title="Define fields and label">
    On the **Fields** tab, create and configure the fields the skill will extract. Label documents in the **Reference** section.
  </Step>

  <Step title="Add and configure NLP activities">
    On the **Activities** tab, add the activities for your scenario (described below). Open each activity in the **Activity Editor** to configure and train it.
  </Step>

  <Step title="Test and publish">
    Click **Test Skill Using Selected Documents** to evaluate [results](/vantage/documentation/advanced-designer/document-skills/results). When the results are good enough, [publish the skill](/vantage/documentation/advanced-designer/document-skills/publish).
  </Step>
</Steps>

## Pre-trained named entities (whole document)

Use this scenario when the entities you need can appear anywhere in the document — for example, company names and addresses in a letter. Add a [Named Entities (NER) activity](/vantage/documentation/advanced-designer/activities/ner) and map each named entity to a field. If you also need to break an address into components (street, city, state, country, postal code), add an [Address Parsing activity](/vantage/documentation/advanced-designer/activities/address-parsing) and map the components to fields.

<Frame>
  <img src="https://mintcdn.com/abbyy/NXewBo345IS17i7w/images/vantage/advanced-designer/ad_usecases_ner.png?fit=max&auto=format&n=NXewBo345IS17i7w&q=85&s=42c1a899cdb1e1b0f0a0837c2dbf32fb" alt="Document processing flow with a Named Entities (NER) activity" width="745" height="132" data-path="images/vantage/advanced-designer/ad_usecases_ner.png" />
</Frame>

## Pre-trained named entities (specific paragraphs)

Use this scenario when the entity always sits in the same paragraph — for example, a purchase amount in the price clause of a sales agreement. First isolate the paragraph with a [Segmentation activity](/vantage/documentation/advanced-designer/activities/segmentation/segmentation-activity), then run a [Named Entities (NER)](/vantage/documentation/advanced-designer/activities/ner) or [Address Parsing](/vantage/documentation/advanced-designer/activities/address-parsing) activity on the segmented field.

You can also isolate the paragraph with a [Fast Learning](/vantage/documentation/advanced-designer/activities/fast-learning) or [NLP Extraction Rules](/vantage/documentation/advanced-designer/activities/nlp-extraction-rules/extraction-rules) activity instead of Segmentation, then run NER or Address Parsing on the result.

<Tip>
  Pre-trained activities are easy to configure and need no training, but a neural network trained on your documents may extract more accurately. If you have a large document set, also try the [custom named entities](#custom-named-entities-deep-learning-for-nlp) scenario below and pick whichever performs better.
</Tip>

<Frame>
  <img src="https://mintcdn.com/abbyy/NXewBo345IS17i7w/images/vantage/advanced-designer/ad_usecases_segmentation_ner_ap.png?fit=max&auto=format&n=NXewBo345IS17i7w&q=85&s=106d6612e3065b43e4ff0cd0f054ac40" alt="Document processing flow with Segmentation feeding Named Entities (NER) and Address Parsing" width="1112" height="103" data-path="images/vantage/advanced-designer/ad_usecases_segmentation_ner_ap.png" />
</Frame>

## Custom named entities (Deep Learning for NLP)

Use this scenario when pre-trained activities can't disambiguate the entities you need — for example, extracting only one organization's name from a paragraph that lists both parties to an agreement, or extracting an entity type that NER doesn't cover (such as an email address). Pair a [Segmentation activity](/vantage/documentation/advanced-designer/activities/segmentation/segmentation-activity) with a [Deep Learning for NLP activity](/vantage/documentation/advanced-designer/activities/deep-learning-nlp): Segmentation isolates the paragraph and Deep Learning extracts the targeted fields.

<Note>
  Training a Deep Learning for NLP activity requires at least 50 documents (150 recommended). For best results, also try the pre-trained [Named Entities (NER)](/vantage/documentation/advanced-designer/activities/ner) activity and pick whichever extracts more accurately on your documents.
</Note>

<Frame>
  <img src="https://mintcdn.com/abbyy/NXewBo345IS17i7w/images/vantage/advanced-designer/ad_usecases_segmentation_dl.png?fit=max&auto=format&n=NXewBo345IS17i7w&q=85&s=b0e1341c863e12fd612cfe8fbb8c57cb" alt="Document processing flow with Segmentation feeding a Deep Learning for NLP activity" width="703" height="81" data-path="images/vantage/advanced-designer/ad_usecases_segmentation_dl.png" />
</Frame>

## Related activities

<CardGroup cols={2}>
  <Card title="Named Entities (NER) activity" icon="tag" href="/vantage/documentation/advanced-designer/activities/ner">
    Extract pre-trained entities like names, organizations, and dates from freeform text.
  </Card>

  <Card title="Address Parsing activity" icon="map-pin" href="/vantage/documentation/advanced-designer/activities/address-parsing">
    Split addresses into street, city, state, country, and postal code.
  </Card>

  <Card title="Segmentation activity" icon="scissors" href="/vantage/documentation/advanced-designer/activities/segmentation/segmentation-activity">
    Isolate the paragraph that contains the data you want to extract.
  </Card>

  <Card title="Deep Learning for NLP activity" icon="brain" href="/vantage/documentation/advanced-designer/activities/deep-learning-nlp">
    Train a neural network to extract custom or hard-to-disambiguate entities.
  </Card>
</CardGroup>
