Triple
T7206544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT dispute settlement system |
E148679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade dispute settlement system |
C1216
|
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: trade dispute settlement system Context triple: [GATT dispute settlement system, instanceOf, trade dispute settlement system]
-
A.
World Trade Organization dispute
A World Trade Organization dispute is a formal legal case between WTO member countries concerning alleged violations of WTO agreements, resolved through the organization’s structured dispute settlement system.
-
B.
international trade dispute
An international trade dispute is a conflict between countries or trading entities over the interpretation, application, or alleged violation of trade agreements, policies, or practices affecting cross-border commerce.
-
C.
WTO mechanism
chosen
The WTO mechanism is the institutional framework and set of rules, procedures, and dispute-settlement processes through which the World Trade Organization governs and facilitates international trade among member countries.
-
D.
trade law
Trade law is the body of rules and principles governing the exchange of goods, services, and capital across borders, including treaties, regulations, and dispute resolution mechanisms between nations and commercial entities.
-
E.
trade policy mechanism
A trade policy mechanism is a structured tool or set of rules—such as tariffs, quotas, subsidies, or trade agreements—used by governments to influence international trade flows, prices, and economic outcomes.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:52 p.m.