Triple
T17746150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeKnight Productions |
E442994
|
entity |
| Predicate | workIncludesRoleOfFounder |
P128628
|
FINISHED |
| Object | showrunner |
—
|
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: showrunner | Statement: [DeKnight Productions, workIncludesRoleOfFounder, showrunner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workIncludesRoleOfFounder Context triple: [DeKnight Productions, workIncludesRoleOfFounder, showrunner]
-
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.
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).
-
C.
founderRole
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
D.
founderAlsoOwns
Indicates that the person or entity who founded something also retains ownership of it.
-
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. 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad26940819090696c2cb86fd606 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:09 a.m.