Triple
T3493589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet–Finnish relations |
E73793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Finland–Soviet Union relations |
C9647
|
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: Finland–Soviet Union relations Context triple: [Soviet–Finnish relations, instanceOf, Finland–Soviet Union relations]
-
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.
soviet
Soviet refers to anything related to the former Soviet Union (USSR), including its government, ideology, culture, or people associated with its socialist, one-party state system.
-
C.
Finnish-American
A Finnish-American is a person in the United States who has full or partial ancestry from Finland, often blending Finnish cultural traditions with American society and identity.
-
D.
region of Finland
A region of Finland is an administrative and geographical area that groups together multiple municipalities for purposes of governance, planning, and regional identity.
-
E.
Cold War relations
chosen
Cold War relations encompass the complex political, military, economic, and ideological interactions between rival blocs—primarily the United States and the Soviet Union and their respective allies—from the late 1940s to the early 1990s, characterized by sustained tension, proxy conflicts, and nuclear deterrence without direct large-scale war between the superpowers.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.