Triple
T22020482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacket exoskeleton suit |
E543831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military technology |
C12898
|
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: fictional military technology Context triple: [Jacket exoskeleton suit, instanceOf, fictional military technology]
-
A.
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.
-
B.
military technology
Military technology encompasses the specialized tools, systems, and innovations developed and used by armed forces to enhance their capabilities in defense, offense, intelligence, and logistics.
-
C.
fictional device
chosen
A fictional device is an imagined tool, machine, or piece of technology that does not exist in reality but is created within a narrative to serve specific plot, thematic, or world-building purposes.
-
D.
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.
-
E.
fictional cyborg
A fictional cyborg is a being that combines organic life with mechanical or electronic enhancements, often exploring themes of identity, humanity, and the boundary between man and machine.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:23 p.m.