Triple
T412397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSR–Cuba military alliance |
E9517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral relationship |
C1070
|
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: bilateral relationship Context triple: [USSR–Cuba military alliance, instanceOf, bilateral relationship]
-
A.
bilateral relations
chosen
Bilateral relations are the political, economic, and diplomatic interactions and agreements that occur directly between two sovereign states.
-
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.
historical relationship
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
D.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
-
E.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.