Relation types

Every cross-module link carries a typed `relation_type`. The type drives the relationship semantics in the entity-links table, the reason-template choice, and the JSON-LD mention emission. Fourteen named relation types cover every connection the platform makes.

Structural relations (T1)

linked_founder

Startup → Founder. The startup’s `founderIds[]` is the FK. Featured on every Startup detail page.

linked_startup

Founder → Startup. `founder.linkedStartupId`. Featured on every Founder profile.

born_from_event

Opportunity / Coverage → Calendar Event. The opportunity or coverage anchored to an event (e.g. accelerator demo day announcement).

Editorial relations (T2)

mentioned_in

Founder / Startup / Event mentioned in an article or coverage. Manually curated by editors. The most common T2 relation.

preparation_resource

File curated as preparation for an Opportunity or Event (e.g. "Read this funding-readiness guide before applying").

follow_up_signal

File / Coverage → Opportunity. After reading a file, here is the open opportunity to apply to. Drives high-intent conversion.

speaker_at

Founder → Event. Editor manually attaches founders to events they speak at.

participant_in

Startup → Event. Cohort participation, sponsorship, pitch competition.

judge_at

Founder → Event. The founder is a judge or panelist at the event.

sponsor_related

Editorial entity → Sponsor organization. When sponsorship context is editorially relevant.

Contextual relations (T3)

same_sector

Two entities share the same sector tag. Score: +25.

same_country

Two entities share the same country. Score: +30.

same_stage

Two startup-related entities share the same stage range. Score: +15.