Triple
T4997666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet diplomacy during World War II |
E112287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic history |
C16758
|
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: diplomatic history Context triple: [Soviet diplomacy during World War II, instanceOf, diplomatic history]
-
A.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
B.
diplomatic relations
Diplomatic relations are the formal and informal interactions and agreements between sovereign states or international actors aimed at managing conflicts, fostering cooperation, and advancing mutual interests through negotiation and representation.
-
C.
diplomatic archive
A diplomatic archive is an organized collection of official records, correspondence, treaties, and related documents produced or received by a state's diplomatic services, preserved for legal, historical, and administrative purposes.
-
D.
diplomatic service
The diplomatic service is a governmental body of professional diplomats and support staff responsible for managing a nation's foreign relations, representing its interests abroad, and conducting negotiations with other states and international organizations.
-
E.
international relations
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
- F. None of above. chosen
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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:34 p.m.