> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/entity-types/importing-types-from-the-textual-library.md).

# Importing types from the Textual library

Textual provides access to a library of entity types that we created from trained models.

These entity types cover a range of additional types of values. You might be able to use these types instead of adding custom types.

You can search for and select types to import that apply to your datasets. The imported types display in the list of custom entity types.

You then [enable the imported types for individual datasets](/textual/entity-types/enabling-entity-types-for-datasets.md).

## Starting the import <a href="#library-type-start-import" id="library-type-start-import"></a>

To start an import, on the **Entity Types** page, either:

* Click **Import type**, then select **Pre-trained library**.
* Click **Add Entity Type**. On the **Add entity type** panel, click **Pre-trained model-based entity types**, then click **Next**.

Textual displays the **Pre-trained Type Library** page.

<figure><img src="/files/xR2WnS7ffY2cqc4rurDc" alt=""><figcaption><p>Library of available types to import into Textual</p></figcaption></figure>

### Information in the type list

For each type, the list includes:

* The name of the type.
* Tags to help categorize the type. For example, a tag might identify a type as being related to government or healthcare.
* Whether the type was imported.

### Filtering the type list

To search for a type based on its name, in the search field, begin to type the name or description text.

To filter the list based on the assigned tags:

1. Click **Filter**.
2. In the tags list, check the tags to include.

## Viewing more detail for a type

When you click the type, the details panel displays.

<figure><img src="/files/WSs2YDOlKZKROubarbX3" alt=""><figcaption><p>Details panel for an entity type in the library</p></figcaption></figure>

The details panel includes:

* The type name.
* Example values.
* Assigned tags.
* A longer description of the type.

## Testing a type

The details panel provides an option to test the type against an input string that you provide. This can help determine if the pre-trained type would detect known values in your files.

When you first display details panel, it includes an example text string that contains a detected value.

To test your own value, in the **Input** text area, type a text string that contains the value to test.

The **Output** text area highlights the type values that were detected in the input string.

## Importing and removing a type

From the type details panel, to import a type, click **Import**.

Textual adds the imported type to the list on the **Entity Types** page.

For a type that is already imported, the **Import** button is replaced with a **Remove** button. To remove the imported type, click **Remove**.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.tonic.ai/textual/entity-types/importing-types-from-the-textual-library.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
