Triple
T33766767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 21 nuclear bomb |
E865251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | US military equipment |
C13536
|
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: US military equipment Context triple: [Mark 21 nuclear bomb, instanceOf, US military equipment]
-
A.
military equipment
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
-
B.
U.S. military ordnance
chosen
U.S. military ordnance encompasses the weapons, ammunition, explosives, and related equipment developed, procured, and used by the United States armed forces for combat and defense operations.
-
C.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
D.
German military equipment
German military equipment encompasses the weapons, vehicles, gear, and support systems designed, produced, or used by German armed forces across different historical periods.
-
E.
U.S. military vehicle
A U.S. military vehicle is a government-owned, purpose-built or modified ground, air, or sea platform designed, equipped, and maintained to support United States armed forces missions, including combat, transport, logistics, reconnaissance, and support operations.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.