Overview
A relationship connects distinct subjects through a specific recorded role or an explicitly labeled contextual evidence candidate.Field groups
- Connection
Field reference
SOURCE_DEPENDENT describes availability; access is a separate product/rights boundary. Null means unknown, not false or zero.Subject
Field ID:relationship.subject. Group: Connection.
The organization or person at the starting end of a recorded connection.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Subject identity must be established separately; a similar name is insufficient.
Relationship type
Field ID:relationship.predicate. Group: Connection.
The recorded semantic connection, such as employment, investment, ownership or manager context.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Retain the actual source-supported type. Do not infer ownership from employment or a personal relationship from co-investment.
Object
Field ID:relationship.object. Group: Connection.
The distinct organization or person at the other end of the connection.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: A relationship does not merge subject and object into one entity.
Context class
Field ID:relationship.context_class. Group: Connection.
Recorded relationship or separately presented evidence candidate.
Defined values: recorded_relationship, evidence_candidate; null when unknown.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: An evidence candidate is a research lead, not a verified identity, personal relationship or guaranteed warm path.
Observed date
Field ID:relationship.observed_date. Group: Connection.
Observation time where exposed on the supporting connection or evidence candidate.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: May be absent. No complete relationship history or general valid-from/valid-to guarantee.
Supporting context
Field ID:relationship.supporting_context. Group: Connection.
An explanation of the supported connection where the view supplies one.
Evidence / dates: Use only the source or event date actually recorded; record modification is not verification.
Limitation: Public or governed source rights apply. A citation URL is not exposed for every connection; customer-private notes are a separate workflow category.
Relationships to other entities
Read subject → predicate → object. Examples include recorded employment, investment, ownership, manager, portfolio and transaction-participant context, only where the particular source supports that type. Publicly observed evidence and governed source information retain their disclosure rights. A source URL or observation date is not exposed on every connection. A related-by-evidence candidate is a research lead. Inferred connections are not included as an offered field state in this reference. Customer-private meetings, notes and inbox/interaction context belong to an authorized Capital workflow. They are separate from these entity fields and are not merged into the public catalog.relationship-context
Fictional request brief, entities, sources, values and dates. This is a documentation example, not a live HTTP response or customer result. Missing dates remain null.Current availability: Reviewed bounded request. Execution: Manual / scoped. Automated invocation: Not currently available. API endpoint: None. MCP execution: None.
- Input
- Result
- Evidence
A research brief for human scope review, not an API payload.