Triple
T25074736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Man’s War |
E628015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military science fiction 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: military science fiction novel Context triple: [Old Man’s War, instanceOf, military science fiction novel]
-
A.
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.
-
B.
military thriller novel
A military thriller novel is a fast-paced, suspenseful story that centers on soldiers, special forces, or military operations, emphasizing tactical action, high-stakes missions, and realistic combat scenarios.
-
C.
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.
-
D.
science-in-fiction novel
A science-in-fiction novel is a narrative that foregrounds real scientific concepts, methods, or communities as central drivers of plot and character, while remaining primarily a work of imaginative fiction rather than speculative science.
-
E.
science fantasy novella
A science fantasy novella is a short, focused work of fiction that blends advanced technology and scientific concepts with magical or supernatural elements in a richly imaginative setting.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:20 a.m.