Triple
T9857954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | evacuation of Tallinn 1941 |
E239635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet naval operation |
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 naval operation Context triple: [evacuation of Tallinn 1941, instanceOf, Soviet naval operation]
-
A.
Kriegsmarine operation
A Kriegsmarine operation is a coordinated naval action planned and executed by Nazi Germany’s navy during World War II to achieve specific military, strategic, or logistical objectives at sea.
-
B.
Soviet campaign
chosen
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
C.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
-
D.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
-
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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.