Triple
T984773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek (2009 film) |
E21253
|
entity |
| Predicate | usesNarrativeDevice |
P7324
|
FINISHED |
| Object | alternate timeline |
—
|
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: alternate timeline | Statement: [Star Trek (2009 film), usesNarrativeDevice, alternate timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNarrativeDevice Context triple: [Star Trek (2009 film), usesNarrativeDevice, alternate timeline]
-
A.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
fictionalNarrator
Indicates that one entity serves as the narrator or storytelling voice within a fictional work that features the other entity.
-
D.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
E.
narrativeFrame
chosen
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4959fe48190a78bd811cbc888ab |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.