# Back Translation A lot of thought needs to go into ways that back-translation can be constrained from hallucinating. Mechanisms for constraining back-translation and avoiding hallucination will range from rigid to flexible. On the rigid end of the spectrum will be methods like Token matching evaluation and `valid_token` constraints. On the more flexible end, we could try pulling in the most similar verses to the back-translation draft and comparing the target-language 'source' in each case. If the model begins to hallucinate, it will probably not match well with existing translations of similar verses. Cipher-based completions (see discussion [here](https://ryder.dev/tokenizing-low-resource-languages/)) might be a way we can mask the tokens from the LLM, but we would need to be sure to offer enough in-context data to ensure useful patterns are detected. --- # 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://codex-editor.gitbook.io/project-accelerate/translators-copilot/translation-assistance/back-translation.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.