Triple
T19755333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quicksilver |
E474486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical science fiction novel |
C31396
|
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: historical science fiction novel Context triple: [Quicksilver, instanceOf, historical science fiction novel]
-
A.
alternate history novel
chosen
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.
-
B.
historical thriller novel
A historical thriller novel is a suspense-driven story that intertwines high-stakes mystery or intrigue with richly detailed, accurately rendered past events and settings.
-
C.
science fiction novel
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.
-
D.
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.
-
E.
historical adventure fiction
Historical adventure fiction is a genre that blends meticulously researched past settings and events with fast-paced, often perilous journeys or quests, emphasizing action, exploration, and personal heroism within a specific historical context.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.