Triple
T15222646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Note Crisis of 1961 |
E363799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet–Finnish relations incident |
C2909
|
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–Finnish relations incident Context triple: [Note Crisis of 1961, instanceOf, Soviet–Finnish relations incident]
-
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.
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.
-
C.
Swedish invasion
A Swedish invasion is a large-scale military incursion initiated by Sweden into foreign territory, typically aimed at conquest, political influence, or strategic advantage.
-
D.
Berlin Airlift
The Berlin Airlift was a massive Allied operation from 1948 to 1949 in which Western powers supplied West Berlin entirely by air after the Soviet Union blockaded all ground routes into the city.
-
E.
diplomatic incident
chosen
A diplomatic incident is an event or action involving representatives of different states that causes tension, conflict, or embarrassment in their official relations.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:12 a.m.