Triple
T20792461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Who: The Invasion of Time |
E511810
|
entity |
| Predicate | companionDepartureContext |
P113678
|
FINISHED |
| Object | Leela remains on Gallifrey |
—
|
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: Leela remains on Gallifrey | Statement: [Doctor Who: The Invasion of Time, companionDepartureContext, Leela remains on Gallifrey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionDepartureContext Context triple: [Doctor Who: The Invasion of Time, companionDepartureContext, Leela remains on Gallifrey]
-
A.
hasCompanionDeparture
Indicates that an entity’s departure is associated with, or accompanied by, the departure of a companion entity.
-
B.
companionDepartureEpisode
Indicates the specific episode in which a companion departs from the primary character or group.
-
C.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
D.
departureStory
chosen
Indicates a narrative or account describing how, why, and under what circumstances an entity left or departed from a place, role, or situation.
-
E.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2910d488190bc4be37512effc86 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.