> 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/dataset-configure-redaction/textual-datasets-synthesis-options/synthesis-options-for-specific-entity-types.md). # Synthesis options for specific entity types The following built-in entity types have additional type-specific synthesis options.


Name Configure synthesis options for name values.	Name synthesis options
Location Configure synthesis options for location values.	Location synthesis options
Email address Configure synthesis options for email address values.	Email address synthesis options
Age Configure synthesis options for age values.	Age synthesis options
Telephone number Configure synthesis options for telephone number values.	Telephone number synthesis options
Date/time Configure synthesis options for date/time values.	Date/time synthesis options
Date of birth Configure synthesis options for date of birth values.	Date of birth synthesis options
Default datetime formats For date/time and date of birth, the formats that Textual supports by default.	Default supported datetime formats

--- # 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/dataset-configure-redaction/textual-datasets-synthesis-options/synthesis-options-for-specific-entity-types.md?ask=&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.