# E.5 Concept Enumerations for characteristicTypeId

This concept enumeration enumeration represents a value that can be applied to the *relationship*.characteristicTypeId field. This is used to indicate that a relationship forms part of the definition of the source concept. The Table below shows the current set of values for this *concept enumeration*.

**Characteristic type (core metadata concept) (900000000000449001)**

<table data-header-hidden data-full-width="true"><thead><tr><th width="342.5433349609375"></th><th></th></tr></thead><tbody><tr><td><strong>Concept</strong></td><td><strong>Comment</strong></td></tr><tr><td><a href="http://snomed.info/id/900000000000006009">900000000000006009 |Defining relationship|</a></td><td><p>A general value which is a <em>supertype</em> of <a href="http://snomed.info/id/900000000000011006">900000000000011006 |Inferred relationship|</a> and <a href="http://snomed.info/id/900000000000010007">900000000000010007 |Stated relationship|</a>.</p><ul><li><em>This value is not applied to any released relationships.</em></li></ul></td></tr><tr><td><a href="http://snomed.info/id/900000000000011006">900000000000011006 |Inferred relationship|</a></td><td><p>Indicates that this defining <em>relationship</em> was inferred by a description logic classifier from the stated view of the <em>concept definition</em>.</p><ul><li><em>Since 2018 the characteristicTypeId of all released relationships has this value. This is because, stated view definitions are now represented by OWL axioms rather than relationships</em>.</li></ul></td></tr><tr><td><strong>Obsolete values that are no longer used</strong></td><td><br></td></tr><tr><td><a href="http://snomed.info/id/900000000000010007">900000000000010007 |Stated relationship|</a></td><td><p>Indicates that this defining <em>relationship</em> was stated by a terminology author.</p><ul><li><em>Not used since 2018 as stated views of concept definitions are now represented using OWL axioms rather than relationships.</em></li></ul></td></tr><tr><td><a href="http://snomed.info/id/900000000000225001">900000000000225001 |Qualifying relationship|</a></td><td><p>The <em>relationship</em> is not part of the definition of the <em>concept</em> but indicates a possible qualification that may be applied to refine a postcoordinated expression that refers to the source <em>concept</em>.</p><ul><li><em>Note used since 2012 when Release Format 2 was introduced.</em></li></ul></td></tr><tr><td><a href="http://snomed.info/id/900000000000227009">900000000000227009 |Additional relationship|</a></td><td><p>The <em>relationship</em> is not part of the definition of the <em>concept</em> but is used to convey some additional information about the <em>concept</em> . This additional information may only be applicable to a particular jurisdiction or use case.</p><ul><li><em>Note used since 2012 when Release Format 2 was introduced.</em></li></ul></td></tr></tbody></table>

***

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Release+File+Specification&#x26;entry.670899847=E.5%20Concept%20Enumerations%20for%20characteristicTypeId" class="button primary">Provide Feedback</a>


---

# 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://docs.snomed.org/snomed-ct-specifications/snomed-ct-release-file-specification/appendices/appendix-e-concept-enumerations/e5-concept-enumerations-for-characteristictypeid.md?ask=<question>
```

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.