Triple
T4961109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea Blitz |
E111408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II bombing |
C1076
|
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 bombing Context triple: [Swansea Blitz, instanceOf, World War II bombing]
-
A.
strategic bombing campaign
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.
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.
-
C.
bombing
chosen
Bombing is the deliberate act of attacking a target by detonating explosive devices, typically from aircraft or planted charges, to cause destruction, damage, or intimidation.
-
D.
batalla de la Segunda Guerra Mundial
Una batalla de la Segunda Guerra Mundial es un enfrentamiento militar específico, terrestre, naval o aéreo, ocurrido entre 1939 y 1945, que involucró fuerzas de las potencias aliadas y/o del Eje con objetivos estratégicos definidos dentro del conflicto global.
-
E.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:32 p.m.