Triple
T30105825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retroactive series |
E765127
|
entity |
| Predicate | fictionalTechnologyRole |
P48208
|
FINISHED |
| Object | drives plot through time jumps |
—
|
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: drives plot through time jumps | Statement: [Retroactive series, fictionalTechnologyRole, drives plot through time jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTechnologyRole Context triple: [Retroactive series, fictionalTechnologyRole, drives plot through time jumps]
-
A.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
B.
fictionalUniverseRole
chosen
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
C.
technologyRole
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
D.
fictionalOccupation
Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity within a fictional context.
-
E.
envisionedTechnology
Indicates that an entity has imagined, conceptualized, or planned a particular technology, typically before it exists or is realized.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 7:09 p.m.