Triple
T35358651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Who: Dark Water |
E1021406
|
entity |
| Predicate | hasCliffhanger |
P116412
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Doctor Who: Dark Water, hasCliffhanger, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCliffhanger Context triple: [Doctor Who: Dark Water, hasCliffhanger, yes]
-
A.
isCliffhangerFor
Indicates that one event, scene, or narrative element ends in suspense and serves as a cliffhanger leading into another.
-
B.
containsCliffhanger
chosen
Indicates that an event, scene, or narrative segment ends in a suspenseful, unresolved way that leaves the outcome uncertain.
-
C.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
-
D.
hasClimaxAt
Indicates that an event, narrative, or process reaches its most intense or decisive point at a specified time, place, or segment.
-
E.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:03 p.m.