Triple
T818131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Nordwind |
E17693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German offensive |
C472
|
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 offensive Context triple: [Operation Nordwind, instanceOf, German offensive]
-
A.
Nazi Germany expansion
Nazi Germany expansion refers to the aggressive territorial and political enlargement of Germany under Adolf Hitler from 1938 to 1941 through annexations, invasions, and occupations that precipitated and escalated World War II in Europe.
-
B.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
C.
European war
chosen
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
D.
German soldiers
German soldiers are military personnel serving in Germany’s armed forces, historically or presently, who are trained, organized, and equipped to conduct defense and combat operations under German command.
-
E.
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.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.