Triple
T26060350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugoslav–Soviet negotiations |
E657240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral relations event |
C24264
|
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 relations event Context triple: [Yugoslav–Soviet negotiations, instanceOf, bilateral relations event]
-
A.
bilateral relations
Bilateral relations are the political, economic, and diplomatic interactions and agreements that occur directly between two sovereign states.
-
B.
bilateral meeting
chosen
A bilateral meeting is a formal or informal discussion between representatives of two distinct parties, typically organizations or countries, to negotiate, coordinate, or resolve specific issues of mutual interest.
-
C.
United States–Russia relations event
A United States–Russia relations event is a specific occurrence, interaction, or development that significantly affects the political, diplomatic, military, economic, or cultural relationship between the United States and Russia.
-
D.
EU–US relations event
An EU–US relations event is a diplomatic, political, or economic occurrence that significantly affects the interactions, policies, or strategic partnership between the European Union and the United States.
-
E.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:16 p.m.