Triple
T9104408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syncopy Inc. |
E218439
|
entity |
| Predicate | hasCoFounderRole |
P87173
|
FINISHED |
| Object | director |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: director | Statement: [Syncopy Inc., hasCoFounderRole, director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoFounderRole Context triple: [Syncopy Inc., hasCoFounderRole, director]
-
A.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
B.
coFounderWith
Indicates that two or more entities jointly founded the same organization or venture.
-
C.
coFounderInvolved
Indicates that an entity shares responsibility for founding another entity and is actively involved in its creation or early development.
-
D.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
E.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca56f1f10819091abadf7cd06c3a6 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:15 p.m.