Triple
T8970749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet interventions in Eastern Europe |
E214259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet foreign policy practice |
C1642
|
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 foreign policy practice Context triple: [Soviet interventions in Eastern Europe, instanceOf, Soviet foreign policy practice]
-
A.
policy of the Soviet Union
chosen
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
B.
United States foreign policy doctrine
A United States foreign policy doctrine is a guiding framework of principles and strategic priorities that shapes how the U.S. engages with other nations and responds to international challenges.
-
C.
Cold War policy
Cold War policy refers to the strategic, political, military, and economic decisions and doctrines adopted by states—primarily the United States and the Soviet Union—to contain, compete with, or influence each other and their allies without escalating into direct large-scale war.
-
D.
foreign policy journal
A foreign policy journal is a periodical publication that analyzes and critiques international relations, diplomatic strategies, and global political developments.
-
E.
foreign policy analysis project
A foreign policy analysis project systematically examines a state or organization’s external actions, decisions, and strategies to understand their causes, consequences, and implications for international 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:02 p.m.