Triple
T11639230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Understanding on Commitments in Financial Services |
E276615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GATS-related instrument |
C6733
|
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: GATS-related instrument Context triple: [Understanding on Commitments in Financial Services, instanceOf, GATS-related instrument]
-
A.
trade in services instrument
A trade in services instrument is a financial or contractual mechanism that facilitates, records, or manages cross-border transactions involving the provision of services rather than physical goods.
-
B.
WTO legal instrument
chosen
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.
tariff liberalization instrument
A tariff liberalization instrument is a policy tool or legal mechanism used to reduce, eliminate, or otherwise relax import and export tariffs to promote trade openness and economic integration.
-
D.
trade policy instrument
A trade policy instrument is a specific tool or measure—such as tariffs, quotas, subsidies, or regulations—used by a government to influence international trade flows and economic outcomes.
-
E.
World Customs Organization instrument
A World Customs Organization instrument is an official legal or technical tool—such as a convention, agreement, standard, or guideline—adopted by the WCO to harmonize and facilitate customs procedures and international trade.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.