relationshiptypes
- Last Updated: May 29, 2026
- 2 minute read
- Semaphore
- Documentation
relationshiptypes allow the user to specify which relationships in the model a rule will be generated for. A rule will only be generated for a concept that has a relationship type matching that defined on the rule.
Applies to
Values
Note: the values of BT (broader term), NT (narrower term), and RT (related term) from previous Semaphore versions are supported for backwards compatibility. They are listed below accordingly.
| Type | Description |
|---|---|
| HigherInHierarchy | All concepts directly (one level) above current concept using any hierarchical relationship. Note: this will not include the Concept Scheme of a Top Concept. |
| LowerInHierarchy | All concepts directly (one level) below current concept using any hierarchical relationship |
| Associative | All concepts associated to the current term using any associative relationship |
| has broader [BT] | All concepts directly (one level) above current concept using the base “has broader” relationship |
| has narrower [NT] | All concepts directly (one level) below current concept using the base “has narrower” relationship |
| has related [RT] | All concepts associated to the current concept using the base “has related” relationship |
| Sub-type | Any hierarchical or associative relationship sub-type defined in the model |
Multiple relationshiptypes can be specified using the pipe character, “|”. So, to generate rules for concepts that are identified as both “has narrower” and “has related” the following syntax can be used: has narrower|has related
Note: the relationshiptypes attribute does not support the use of the ‘^’ character to exclude relationshiptypes.
Example 1
For a model that contains the concept ‘Drug Trafficking’ with a “has broader” concept of ‘Crime, Law and Justice’ and “has related” associative relationships to ‘Drug Enforcement Agency’ and to ‘Organized Crime’, the following relationshiptypes would be assigned:
| concept | relationshiptype |
|---|---|
| Crime, Law and Justice | has broader, BT, HigherInHierarchy |
| Drug Enforcement Agency | has related, RT, Associative |
| Organized Crime | has related, RT, Associative |
Using the following template rule:
<linklist label="link.RULEBASE_CLASS.WORD_FIELD.LANGUAGE.ID_FIELD_EVIDENCE" weight="25" relationshiptypes="Associative"/>
would generate the output:
<link label="link.Topic.Drug Enforcement Agency.en.6e53c97f-61a6-41d0-bdad-cee681aeddf2_EVIDENCE" weight="25"/>
<link label="link.Topic.Organized Crime.en.291b557b-57d1-4177-a668-fb4380fb52b9_EVIDENCE" weight="25"/>
Example 2
For a model that contains the concept ‘Apple, Inc’ with a “has broader” concept of ‘Companies’ and associative relationship sub-types of ‘has CEO’ - ‘Tim Cook’, ‘has Industry’ - ‘Consumer Electronics’ and ‘Produces Products’ - ‘iPad’, ‘iPhone’, ‘MacBook’, the following relationshiptypes would be assigned:
| concept | relationshiptype |
|---|---|
| Companies | has broader, BT, HigherInHierarchy |
| Tim Cook | has CEO, Associative |
| Consumer Electronics | has Industry, Associative |
| iPad | Produces Products, Associative |
| iPhone | Produces Products, Associative |
| MacBook | Produces Products, Associative |
Using the following template rule:
<linklist label="link.RULEBASE_CLASS.WORD_FIELD.LANGUAGE.ID_FIELD_EVIDENCE" weight="25" relationshiptypes="Produces Products"/>
would generate the output:
<link label="link.Topic.iPad.en.1248e6e2-2252-40d6-9453-2cfeacf342c0_EVIDENCE" weight="25"/>
<link label="link.Topic.iPhone.en.5c0986f6-8c04-4983-b5a2-3a2a704d089b_EVIDENCE" weight="25"/>
<link label="link.Topic.Macbook.en.e0b6ef10-0860-4f2c-979c-93ad5aeec024_EVIDENCE" weight="25"/>