Triple
T38213415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Impossible Planet |
E1010616
|
entity |
| Predicate | airOrderInSeries |
P90018
|
FINISHED |
| Object | 8th episode of Series 2 (2005) Doctor Who |
—
|
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: 8th episode of Series 2 (2005) Doctor Who | Statement: [The Impossible Planet, airOrderInSeries, 8th episode of Series 2 (2005) Doctor Who]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airOrderInSeries Context triple: [The Impossible Planet, airOrderInSeries, 8th episode of Series 2 (2005) Doctor Who]
-
A.
airingOrder
chosen
Indicates the sequence in which items (such as episodes or installments) are broadcast or released to the public.
-
B.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
C.
orderingType
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
-
D.
arrivalOrder
Indicates the relative sequence in which entities arrive, specifying which one comes before or after another.
-
E.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.