> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-compositional-grammar-specification/implementation-guidance/7.7-classifying.md).
# Classifying
In order to automatically understand the inferred relationships between SNOMED CT expressions and/or precoordinated concepts, the expressions should be classified using a semantic reasoner. A number of reasoners exist, such as Snorocket, ELK and FACT++, which can classify and reason over OWL 2 EL.
Before a SNOMED CT compositional grammar expression can be classified using one of these reasoners, it must first be parsed, normalised and then translated into OWL 2 EL. The specific normalisation transformations that are required prior to translation into OWL include:
* Grouping all ungrouped attributes with a relationship type that is allowed to be grouped, and
* Transforming expressions to ensure that they conform to the concept model – in particular, where a laterality refinement has been applied to a focus concept that is not subsumed by [123037004 | Body structure|](http://snomed.info/id/123037004) , apply this laterality to all lateralisable finding sites within the definition of this focus concept.
The translation into OWL can then be performed in a variety of programming languages, including Perl.
Provide Feedback
---
# 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.snomed.org/snomed-ct-specifications/snomed-ct-compositional-grammar-specification/implementation-guidance/7.7-classifying.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.