Triple
T14263099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATT security exceptions dispute |
E353573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade dispute involving security exceptions |
C12703
|
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 involving security exceptions Context triple: [GATT security exceptions dispute, instanceOf, trade dispute involving security exceptions]
-
A.
international trade dispute
chosen
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.
-
B.
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.
-
C.
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.
-
D.
trade embargo
A trade embargo is a government-imposed restriction that partially or completely prohibits commercial exchange of goods and services with a specific country, group, or entity for political, economic, or security reasons.
-
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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.