Triple
T1875149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stakhanovite movement |
E39126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet campaign |
C7832
|
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: Soviet campaign Context triple: [Stakhanovite movement, instanceOf, Soviet campaign]
-
A.
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.
-
B.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
-
C.
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.
-
D.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
-
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. chosen
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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:34 p.m.