Triple
T38689901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruhrstahl SD 1400 X |
E949231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II aerial bomb |
C9334
|
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: World War II aerial bomb Context triple: [Ruhrstahl SD 1400 X, instanceOf, World War II aerial bomb]
-
A.
aerial bomb
chosen
An aerial bomb is an explosive weapon designed to be dropped from aircraft to detonate on or near a target, causing destructive blast, fragmentation, or specialized effects.
-
B.
World War II aircraft
World War II aircraft are military airplanes designed, produced, and deployed between 1939 and 1945 for roles such as fighters, bombers, transports, and reconnaissance in support of the war’s air operations.
-
C.
World War I bomber
A World War I bomber is a military aircraft designed and used during the First World War to carry and drop bombs on enemy targets, including strategic infrastructure, troop concentrations, and supply lines.
-
D.
World War II weapon
A World War II weapon is any tool, device, or system—ranging from small arms and artillery to aircraft, naval vessels, and emerging technologies like rockets and atomic bombs—designed and employed by nations between 1939 and 1945 to inflict damage, gain strategic advantage, or defend against enemy forces.
-
E.
bomber aircraft project
A bomber aircraft project is a coordinated effort to design, develop, test, and produce an aircraft optimized for delivering explosive ordnance to ground or sea targets under specified operational requirements.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.