Triple
T29299344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2D Entertainment |
E742917
|
entity |
| Predicate | hasFounderRoleOfSuriya |
P172773
|
FINISHED |
| Object | 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: co-founder | Statement: [2D Entertainment, hasFounderRoleOfSuriya, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderRoleOfSuriya Context triple: [2D Entertainment, hasFounderRoleOfSuriya, co-founder]
-
A.
sonWithSurya
Indicates a parent-child relationship where the entity is a son in relation to Surya.
-
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.
hasBrandFounderRole
Indicates that an entity holds or has held the role of founder for a particular brand.
-
D.
coFounderOfProducingCompany
Indicates that an entity is a co-founder of a particular producing company, sharing founding responsibility with one or more others.
-
E.
hasFounderRelationship
chosen
Indicates a relationship where one entity serves as the founder or co-founder of another entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 1:09 p.m.