Triple
T3379770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia – Measures Concerning Traffic in Transit (DS512) |
E71153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | WTO panel proceeding |
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: WTO panel proceeding Context triple: [Russia – Measures Concerning Traffic in Transit (DS512), instanceOf, WTO panel proceeding]
-
A.
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.
-
B.
WTO legal instrument
A WTO legal instrument is a formal, binding or non-binding document adopted within the World Trade Organization framework that establishes, interprets, or implements rules, commitments, or procedures governing international trade among its members.
-
C.
WTO law concept
A WTO law concept is a legal notion or principle that governs international trade relations among World Trade Organization members under its agreements and dispute settlement system.
-
D.
trade policy review process
The trade policy review process is a systematic, periodic evaluation of a country's trade policies and practices to assess their transparency, consistency with international rules, and impact on global trade.
-
E.
WCO body
A WCO body is a standardized, structured representation of data and metadata defined by the World Customs Organization to facilitate consistent, electronic exchange of customs-related information across international systems.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:14 p.m.