Triple
T37770479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon V |
E941532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional supersoldier program |
C66534
|
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 supersoldier program Context triple: [Weapon V, instanceOf, fictional supersoldier program]
-
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.
fictional government project
chosen
A fictional government project is an imagined, often secretive or experimental initiative undertaken by a governmental body within a narrative to drive plot, explore themes, or create speculative scenarios.
-
C.
genetically engineered superhuman
A genetically engineered superhuman is an individual whose DNA has been deliberately modified to enhance physical, mental, or other abilities far beyond typical human limits.
-
D.
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.
-
E.
super-soldier group
A super-soldier group is an elite, often clandestine military unit composed of individuals enhanced beyond normal human limits through advanced technology, genetic modification, or rigorous experimental training to perform high-risk, high-impact missions.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.