Triple
T1298106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex on Telecommunications |
E27699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade in services instrument |
C6734
|
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 in services instrument Context triple: [Annex on Telecommunications, instanceOf, trade in services instrument]
-
A.
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.
-
B.
WTO mechanism
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.
-
C.
ILO instrument
An ILO instrument is a formal legal document—such as a convention, recommendation, or protocol—adopted by the International Labour Organization to set international labor standards and guide member states’ labor policies and practices.
-
D.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
E.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
- F. None of above. chosen
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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.