# Synonims Synonyms can be used whenever an entity value could be expressed in different ways but you still need the original value passed to your chatbot. For example: ``` I live in New York I live in the big apple ``` The above expressions are both referring to New York. By default, we could add both New York and Big Apple to the entity location and the AI engine would be perfectly capable of parsing both. ![](/files/-LeMnLAM8GkyN8_PhL3s) The problem comes when we would like to have all variations (big apple) to point to an original value (New York) as we do need to have a unique value in our chatbot. To accomplish this, we simply move big apple on the same line as new york, inside brackets: ![](/files/-LeMnnIB9T38BWH_CWb9) This notation will tell Xenioo that Big Apple is a synonym of New York and that, while it should be accepted as a possible value, should be translated back to the main value when passed as a variable. Going back to our example, both of the expression would now both create a location variable valued New York. Additional synonyms can be specified by just separating them with a comma and there's no limit to the number of synonyms you can add for each entity. Standard entity notation for alternate values continue of course to be possible. ![](/files/-LeMosrrNSuoCfrOhsH0) --- # Agent Instructions: 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: ``` GET https://docs10.xenioo.com/ai/entities/synonims.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.