Triple
T2681150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SALT I Interim Agreement |
E56575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States–Soviet Union agreement |
C824
|
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: United States–Soviet Union agreement Context triple: [SALT I Interim Agreement, instanceOf, United States–Soviet Union agreement]
-
A.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
C.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
United Nations–brokered accord
A United Nations–brokered accord is a formal agreement between parties, typically states or factions, negotiated and facilitated by the UN to resolve conflicts, address global issues, or establish cooperative frameworks under international law.
-
E.
United Nations–brokered accord
A United Nations–brokered accord is a formal agreement between parties, typically states or factions, negotiated and facilitated by the UN to resolve conflicts, manage disputes, or establish cooperative frameworks under international oversight.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:54 p.m.