Triple
T3599190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baedeker Blitz |
E76213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German strategic bombing campaign |
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: German strategic bombing campaign Context triple: [Baedeker Blitz, instanceOf, German strategic bombing campaign]
-
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.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
C.
World War II offensive
A World War II offensive is a coordinated, large-scale military campaign conducted by one or more nations to seize strategic objectives, weaken enemy forces, or shift the balance of the war in a specific theater or front.
-
D.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
E.
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.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.