Triple
T26226699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorized Economic Operator (AEO) programme in India |
E655909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade facilitation scheme |
C44067
|
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 facilitation scheme Context triple: [Authorized Economic Operator (AEO) programme in India, instanceOf, trade facilitation scheme]
-
A.
trade facilitation initiative
chosen
A trade facilitation initiative is a coordinated set of policies, measures, and projects designed to simplify, modernize, and harmonize international trade procedures to reduce costs and improve the efficiency of cross-border commerce.
-
B.
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.
-
C.
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.
-
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 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.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:58 p.m.