Triple
T5382148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nom.com |
E113109
|
entity |
| Predicate | founderRoleOfSteveChen |
P7059
|
FINISHED |
| Object | YouTube co-founder |
—
|
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: YouTube co-founder | Statement: [Nom.com, founderRoleOfSteveChen, YouTube co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderRoleOfSteveChen Context triple: [Nom.com, founderRoleOfSteveChen, YouTube co-founder]
-
A.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
B.
founderRole
chosen
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
C.
currentFounder
Indicates that an entity is a present, active founder of another entity (such as an organization or company).
-
D.
coFounderOccupation
Indicates that the specified occupation is or was held by a person in their role as a co-founder of an organization.
-
E.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.