Triple
T5751050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All You Need Is Kill |
E126852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military science fiction work |
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 work Context triple: [All You Need Is Kill, instanceOf, military science fiction work]
-
A.
fictional interstellar war
A fictional interstellar war is a large-scale, imagined conflict between civilizations or factions across multiple star systems, often involving advanced technology, alien species, and complex political or ideological struggles.
-
B.
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.
-
C.
science fiction hero
A science fiction hero is a courageous protagonist who confronts extraordinary futuristic or extraterrestrial challenges, often using advanced technology, intellect, or unique abilities to protect others and shape the fate of worlds.
-
D.
science fiction movement
A science fiction movement is a collective trend or school within science fiction characterized by shared themes, aesthetics, and narrative approaches that respond to particular cultural, technological, or philosophical concerns.
-
E.
science fiction film
A science fiction film is a motion picture that explores speculative concepts such as advanced technology, space travel, time manipulation, or extraterrestrial life, often examining their impact on individuals and societies.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:48 p.m.