> For the complete documentation index, see [llms.txt](https://docs.3dolphins.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3dolphins.ai/bot-settings/dialog-flows/untitled-1/defined-intention-and-entity-from-user-response.md).
# Intention and Entity
When creating a dialogue, the first thing you need to do is define the **Intention** and **Entity**. An **intention** represents the purpose of a user’s input. You define an intent for each type of user request. An **entity** represents a term or object that is relevant to your intents and that provides a specific context for an intent.
Type the word that you wanna used to be your intention and entity (able more than one). Then, Select the word that will be used as the **intention** or **entity** (if you want defined intention you can type on the entity field as intention). You can also delete and edit the intention & entity that has been created.
For example, if you want to add a dialog about 'Station,' you can include several questions such as 'nearest station' and 'station near Juanda.' Add as many relevant questions as possible for this scenario. 'Station' and 'nearest station' are **Intents**, while 'Juanda' is an **Entity** with the name **location**.
Besides adding the intention and entity one by one, you may add several entities at once in one sentence. This is also known as **Multi Entity**. For example, the nearby station from Juanda at 5 pm. The nearby station is an **Intention**, Juanda is **Entity** name location, and 5.pm is **Entity** name time.
Intention and Entity
After you have finished creating the intent and entity, click the next button to proceed to step 2 **Prompt Response** by clicking the **'Next'** button.
---
# 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.3dolphins.ai/bot-settings/dialog-flows/untitled-1/defined-intention-and-entity-from-user-response.md?ask=&goal=
```
`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.