Triple
T14253666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Lock |
E353331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional temporal security mechanism |
C12898
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: fictional temporal security mechanism Context triple: [Time Lock, instanceOf, fictional temporal security mechanism]
-
A.
Fictional time machine
A fictional time machine is a device or mechanism that enables characters to travel to different points in time, often serving as a narrative tool to explore alternate histories, futures, and the consequences of altering events.
-
B.
Time-travel device
A time-travel device is a mechanism or apparatus that enables users to move between different points in time, altering or observing past and future events.
-
C.
fictional device
chosen
A fictional device is an imagined tool, machine, or piece of technology that does not exist in reality but is created within a narrative to serve specific plot, thematic, or world-building purposes.
-
D.
time traveler
A time traveler is an individual who moves between different points in time, intentionally or accidentally, experiencing and potentially altering events across past, present, and future.
-
E.
fictional time period
A fictional time period is an invented span of time, often with its own history, events, and cultural context, created by an author to serve as the temporal setting for a narrative or world.
- F. None of above.
Provenance (1 batch)
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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.