Triple
T36222062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinn King |
E1047874
|
entity |
| Predicate | roleInEverlasting |
P203429
|
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: [Quinn King, roleInEverlasting, showrunner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEverlasting Context triple: [Quinn King, roleInEverlasting, showrunner]
-
A.
roleInRolandLife
Indicates that one entity holds a particular role or significance in the life or personal experience of Roland.
-
B.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
C.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
D.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
E.
roleInNappilyEverAfter
Indicates that an entity has a role or participation in the work "Nappily Ever After."
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
| PDg | Predicate description generation | batch_6a017bc16860819090d47f1c2db1ca88 |
completed | May 11, 2026, 6:48 a.m. |
Created at: May 3, 2026, 4:09 p.m.