Triple
T29814179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of 23 February 1945 |
E757058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied air raid |
C179
|
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: Allied air raid Context triple: [bombing of 23 February 1945, instanceOf, Allied air raid]
-
A.
strategic bombing campaign
chosen
A strategic bombing campaign is a sustained aerial offensive aimed at weakening an enemy’s war-making capacity and morale by targeting key industrial, military, and infrastructural assets rather than solely engaging frontline forces.
-
B.
airborne invasion
An airborne invasion is a large-scale military assault in which troops, equipment, and supplies are deployed from the air—typically by parachute or aircraft landing—behind or beyond enemy lines to seize and hold key objectives.
-
C.
Strategic bombing force
A strategic bombing force is a military aviation unit organized, equipped, and trained to conduct long-range, high-impact bombing campaigns against an adversary’s critical infrastructure, industry, and strategic assets to weaken their capacity and will to wage war.
-
D.
naval bombardment
Naval bombardment is the use of warships’ long-range weapons to attack targets on land or at sea, typically to weaken enemy defenses, infrastructure, or forces.
-
E.
World War II commando raid
A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:25 p.m.