Triple
T8361486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bid Time Return |
E197016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | time travel novel |
C916
|
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: time travel novel Context triple: [Bid Time Return, instanceOf, time travel novel]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
science fiction novel
chosen
A science fiction novel is a long-form narrative that explores speculative futures, advanced technologies, or alternative realities to examine their impact on individuals, societies, and the nature of existence.
-
E.
time-traveling species
A time-traveling species is a group of organisms or beings capable of intentionally moving themselves or others across different points in time, thereby experiencing and potentially altering multiple historical or future eras.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6 p.m.