Triple
T21485770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom import regime for colonial goods |
E530112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade policy regime |
C44852
|
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 policy regime Context triple: [United Kingdom import regime for colonial goods, instanceOf, trade policy regime]
-
A.
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.
-
B.
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.
-
C.
trade policy expert
A trade policy expert is a specialist who analyzes, designs, and advises on international trade rules, agreements, and regulations to guide governments or organizations in achieving economic and strategic objectives.
-
D.
protectionist trade policy
Protectionist trade policy is a government strategy that restricts imports and/or promotes domestic industries through tools like tariffs, quotas, and subsidies to shield the national economy from foreign competition.
-
E.
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.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:21 p.m.