> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/open-end-cleaning-and-coding/introduction-to-oe-coding/step-4-configure-coding.md).
# 4. Review the entity glossary
After the mapping is saved, Metaforms builds an entity glossary from the mapped response columns. The glossary helps preserve and normalize important names during later AI processing.
Entities are organized by question and source:
* **Merge from responses:** entities found in actual answers
* **Add suggestions:** AI-suggested entities
* **Review uploads:** entries from an uploaded masterlist
For each question, you can:
* Select or clear an entity to control whether it is included.
* Edit the canonical entity name.
* Add or remove name variants.
* Add a new entity manually.
* Remove an entity.
You can also select **Add entities from a file** to upload an `.xlsx`, `.xls`, or `.csv` brand/entity list. Metaforms suggests which questions the uploaded entities belong to.
When the glossary is correct, select **Confirm entity glossary**. If Metaforms found no entities, you can still confirm an empty glossary.
---
# 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://help.metaforms.ai/open-end-cleaning-and-coding/introduction-to-oe-coding/step-4-configure-coding.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.