Triple
T21812536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex 2 of the WTO Agreement |
E538513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dispute settlement agreement |
C3028
|
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: dispute settlement agreement Context triple: [Annex 2 of the WTO Agreement, instanceOf, dispute settlement agreement]
-
A.
legal settlement
chosen
A legal settlement is an agreement between disputing parties to resolve a legal claim or lawsuit, typically involving negotiated terms such as payment or actions, without proceeding to a final court judgment.
-
B.
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.
-
C.
multistate settlement agreement
A multistate settlement agreement is a coordinated legal resolution in which multiple state authorities jointly negotiate and finalize terms with one or more parties to resolve common claims or regulatory issues across their jurisdictions.
-
D.
settlement policy
Settlement policy is a set of principles and rules that govern how disputes are resolved and agreements are reached, typically outlining procedures, criteria, and terms for negotiating and finalizing settlements.
-
E.
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.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.