Triple
T33659390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Terro-Human Future History |
E862309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | future history series |
C58672
|
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: future history series Context triple: [The Terro-Human Future History, instanceOf, future history series]
-
A.
future history
chosen
A future history is a speculative narrative framework that chronicles imagined events and developments over an extended period of future time, often outlining the rise and fall of societies, technologies, and cultures.
-
B.
science fiction historian
A science fiction historian researches, analyzes, and documents the development, themes, cultural impact, and evolution of science fiction across various media and historical periods.
-
C.
alternate history novel
An alternate history novel is a work of fiction that explores how events might unfold in a world where key historical moments occurred differently from how they did in reality.
-
D.
hard science fiction series
A hard science fiction series is a collection of stories that emphasize scientific accuracy, rigorous technological detail, and plausible extrapolation of real-world science to explore speculative futures or phenomena.
-
E.
science fiction anthology series
A science fiction anthology series is a collection of standalone episodes or stories, each exploring different speculative concepts, settings, and characters within the broader genre of science fiction.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.