Triple
T17496068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White forces (Finnish Civil War) |
E426063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | belligerent in the Finnish Civil War |
C23957
|
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: belligerent in the Finnish Civil War Context triple: [White forces (Finnish Civil War), instanceOf, belligerent in the Finnish Civil War]
-
A.
engagement of the Finnish Civil War
An engagement of the Finnish Civil War is a discrete military confrontation between opposing Red and White forces, typically involving organized combat over a specific location or objective within the broader 1918 conflict.
-
B.
belligerent in war
A belligerent in war is a state or organized party that is legally recognized as actively engaged in armed conflict, possessing rights and obligations under the laws of war.
-
C.
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.
-
D.
belligerent force
chosen
A belligerent force is an organized military or armed group that actively participates in hostilities during an armed conflict.
-
E.
side in the Russian Civil War
A side in the Russian Civil War represents one of the organized political, military, or social factions (such as the Reds, Whites, Greens, or foreign interventionists) that pursued distinct goals and alliances in the multi-front conflict following the Russian Revolution.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.