Triple
T24531535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbitration Agreement of 1971 between Argentina and Chile |
E606823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arbitration agreement |
C3153
|
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: arbitration agreement Context triple: [Arbitration Agreement of 1971 between Argentina and Chile, instanceOf, arbitration agreement]
-
A.
arbitration legislation
Arbitration legislation is the body of laws and regulations that governs how disputes are resolved through arbitration instead of traditional court litigation, defining procedures, rights, and enforcement of arbitral awards.
-
B.
arbitration law case
An arbitration law case is a legal dispute resolved through a private adjudicative process governed by arbitration agreements and relevant statutes, rather than by traditional court litigation.
-
C.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
-
D.
alternative dispute resolution program
An alternative dispute resolution program is a structured process that uses methods such as mediation, arbitration, or negotiation to help parties resolve conflicts outside of traditional court litigation.
-
E.
antitrust agreement
An antitrust agreement is a formal or informal arrangement between two or more independent economic entities that coordinates their competitive behavior in a way that may restrict competition, such as fixing prices, limiting output, or dividing markets.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:25 a.m.