Triple
T166624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Case Blue |
E3029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht offensive |
C635
|
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: Wehrmacht offensive Context triple: [Case Blue, instanceOf, Wehrmacht offensive]
-
A.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
B.
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.
-
C.
World War II campaign
chosen
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.
-
D.
amphibious invasion
An amphibious invasion is a coordinated military operation in which armed forces assault a hostile or potentially hostile shore by deploying troops, vehicles, and equipment from the sea onto land.
-
E.
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.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.