Triple
T36693607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War communications |
E906026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic communications system |
C11917
|
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 communications system Context triple: [Cold War communications, instanceOf, diplomatic communications system]
-
A.
diplomatic cable
A diplomatic cable is a confidential, formal written communication sent between a country's diplomatic missions and its home government to report information, convey policy positions, or request instructions.
-
B.
global communication system
chosen
A global communication system is an interconnected network of technologies, protocols, and infrastructures that enables real-time exchange of information across the world regardless of geographic location.
-
C.
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.
-
D.
diplomatic convention
A diplomatic convention is a formal international agreement or treaty that establishes rules, procedures, or standards governing relations and conduct between states.
-
E.
diplomatic site
A diplomatic site is a designated location, such as an embassy, consulate, or mission, where official representatives of one state conduct formal relations, negotiations, and services within another state or international organization.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.