Some derived relation types (DRTs) are ready for you to use immediately and are already integrated into other products. These are called out-of-the-box (OOTB) derived relation types.
List of OOTB DRTs
The following table contains OOTB derived relation types, which you can also find on the Relation types page in the Operating Model settings. You can identify derived relation types on the Relation types page by checking the Kind column. If the value in the Kind column for a relation type is Derived, the relation type is a derived relation type.
| Head | Role | Co-role | Tail | Public ID |
|---|---|---|---|---|
| AI Agent | can be accessed through | provides access to | AI Endpoint | AIAgentAccessibleThroughAIEndpoint |
| AI Agent | can consult data source | can be consulted via | Inference Data | AIAgentCanReadDataSource |
| AI Agent | can manipulate data in | can be manipulated via | Output Data | AIAgentCanManipulateDataSource |
| AI Agent | infers using LLM | is used for inference of | AI Model | AgentInvokesModel |
| AI Agent | is monitored by | monitors | AI Monitor | AIAgentMonitoredByAIMonitor |
| AI Agent | uses | is used by | AI Agent | AIAgentCallsAIAgent |
| AI Base Model | has inference category | is inference category of | Data Category | AIBaseModelInfersFromDataCategory |
| AI Base Model | has output category | is output category of | Data Category | AIBaseModelHasOutputDataCategory |
| AI Base Model | has training category | is training category of | Data Category | AIBaseModelIsTrainedByDataCategory |
| AI Model Version | has training category | is training category of | Data Category | AIModelVersionIsTrainedByDataCategory |
| AI Model Version | has output category | is output category of | Data Category | AIModelVersionHasOutputDataCategory |
| AI Model Version | complies to | applies to | Policy | AiModelCompliesToPolicy |
| AI Model Version | has inference category | is inference category of | Data Category | AIModelVersionInfersFromDataCategory |
| AI Use Case | complies to | applies to | Policy | AiUseCaseCompliesToPolicy |
| AI Use Case | has output | is output of | Data Category | AiUseCaseHasOutputDataCategory |
| AI Use Case | infers from | infers | Data Category | AiUseCaseUsesInfersFromDataCategory |
| AI Use Case | is trained by | trains | Data Category | AiUseCaseIsTrainedByDataCategory |
| Data Entity | represents | represented by | Table | DataEntityRepresentsTable |
| Data Product | is categorized by | categorizes | Data Category | DataProductIsCategorizedByDataCategory |
| Data Product Port | is categorized by | categorizes | Data Category | DataProductOutputPortIsCategorizedByDataCategory |
| Data Product Port | is implemented by | implements | Table | DataProductOutputPortIsImplementedByTable |
| Measure Source | is used to calculate | is calculated using | Measure | MeasureSourceIsUsedToCalculateMeasure |
| Referencing Asset | refers to | is referred to | Business Asset | ReferencingAssetRefersToBusinessAsset |
Customizing an OOTB DRT
Although OOTB derived relation types are managed by the system, you can customize the following elements:
- Definition: You can edit the role, co-role, and description to better match your organization's terminology.
- New relation paths: You can add your own relation paths alongside the existing ones. To ensure system stability, you can't edit or delete OOTB relation paths.
Public IDs of OOTB and system-managed derived relation types can't be edited.
Guidelines for the relation type builder
If an OOTB derived relation type is shown on the Relation type builder tab, you can add only new straight relation paths. You can edit or delete the relation paths that you added yourself.
Guidelines for the JSON editor
Most OOTB derived relation types contain multiple optimized relation paths, which is why they can be viewed or edited only via the JSON tab. When working in the JSON editor, there are a few specific guidelines to follow:
- Creating connections: Any new relation path that you add must start from the head and reach the tail, either directly or through any new node that you add.
- Protected elements: A relation path that you add can leave only the head node or any node that you added. It can reach only the tail node or any node that you added. Your relation path can't touch an intermediate OOTB node.
- Identifying system code: You may notice elements labeled with "system": true, which indicates that the elements are read-only. If you try to edit these protected elements, your changes are reverted. You can edit or delete only the elements that you added.