Triple
T26002311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Soviet arms control process |
E646663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral negotiation process |
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 negotiation process Context triple: [United States–Soviet arms control process, instanceOf, bilateral negotiation process]
-
A.
multilateral negotiation process
A multilateral negotiation process is a structured series of interactions among three or more parties with differing interests, aimed at reaching mutually acceptable agreements through communication, bargaining, and compromise.
-
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.
alternating-offers bargaining game
An alternating-offers bargaining game is a strategic interaction in which two or more parties sequentially propose and respond to offers over how to divide a surplus, with the possibility of delay affecting payoffs and outcomes.
-
D.
bilateral diplomatic agreement
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
-
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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9 a.m.