Triple
T9741314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sound Ventures |
E236191
|
entity |
| Predicate | hasCoFounderOccupation |
P55842
|
FINISHED |
| Object | actor |
—
|
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: actor | Statement: [Sound Ventures, hasCoFounderOccupation, actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoFounderOccupation Context triple: [Sound Ventures, hasCoFounderOccupation, actor]
-
A.
coFounderOccupation
chosen
Indicates that the specified occupation is or was held by a person in their role as a co-founder of an organization.
-
B.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
C.
hasCoFounderRole
Indicates that an entity holds or is assigned the role of co-founder in relation to another entity (such as an organization or project).
-
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.
Provenance (3 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2af3e48190b83a442cd0e84062 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.