Triple
T21485772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom import regime for colonial goods |
E530112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial preference system |
C19162
|
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: imperial preference system Context triple: [United Kingdom import regime for colonial goods, instanceOf, imperial preference system]
-
A.
preferential trade agreement
chosen
A preferential trade agreement is an arrangement between two or more countries to reduce tariffs and other trade barriers on certain products or services for member nations, granting them more favorable access than non-members.
-
B.
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.
-
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.
customs tariff
A customs tariff is a government-imposed tax on imported (and sometimes exported) goods, typically used to regulate trade, protect domestic industries, and generate revenue.
-
E.
transatlantic trade system
The transatlantic trade system was a network of economic exchanges linking Europe, Africa, and the Americas, involving the movement of goods, enslaved people, and raw materials across the Atlantic Ocean from the 16th to 19th centuries.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:21 p.m.