> 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/about-entity-types.md).

# About entity types

An entity type is a category of entity value. For example, the entity value John might be an example of the Given Name entity type.

Tonic Textual comes with a [built-in set of entity types that are detected by default](/textual/entity-types/built-in-entity-types.md). These include the more common entity types such as names and locations.

Textual also provides a [library of additional types that you can import into Textual](/textual/entity-types/entity-type-export-import/importing-types-from-the-textual-library.md) and use in your datasets.

You can also configure custom entity types, which you can use to detect values that are not covered by the built-in entity types or the types in the library.

When you create a custom entity type, you can either:

* [Use regular expressions to identify matching values.](/textual/entity-types/entity-types-custom.md) You might use this option when there are a limited number of values, or if the values follow specific formats that can easily be identified with a regular expression.
* [Define and train a model to identify matching values.](/textual/entity-types/entity-type-custom-model.md) Training a model is an iterative process that can take hours or days, depending on your data.\
  \
  You might create this type of custom entity when there are a large number of values that do not follow a specific format. The values need to be identified more by context.

You can also view this [video overview of entity types and entity type handling](https://youtu.be/05x8utCTYGY). 


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/textual/entity-types/about-entity-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.