Triple
T27186548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Unit universe |
E683349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military fiction setting |
C13224
|
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 fiction setting Context triple: [The Unit universe, instanceOf, military fiction setting]
-
A.
fictional military siege
A fictional military siege is a prolonged, often strategically complex encirclement and assault on a fortified location within a narrative, used to create tension, test characters, and explore themes of endurance, sacrifice, and conflict.
-
B.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
C.
fictional setting
chosen
A fictional setting is an imagined world or environment, with its own locations, cultures, and rules, in which the events of a story take place.
-
D.
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.
-
E.
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.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:30 a.m.