Triple
T3664243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomsday |
E77721
|
entity |
| Predicate | partOfStoryArc |
P24126
|
FINISHED |
| Object | Torchwood arc |
—
|
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: Torchwood arc | Statement: [Doomsday, partOfStoryArc, Torchwood arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfStoryArc Context triple: [Doomsday, partOfStoryArc, Torchwood arc]
-
A.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
B.
firstMajorStoryArc
Indicates that the related entity represents the initial or earliest major story arc associated with another narrative work or series.
-
C.
partOfSeriesOfEvents
Indicates that an event is one element within a larger, ordered sequence of related events.
-
D.
storyline
chosen
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
E.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fe5eb08190ab15044acf9ac8a9 |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.