Triple
T36714800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Generalized System of Preferences |
E906886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tariff preference scheme |
C19993
|
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: tariff preference scheme Context triple: [United States Generalized System of Preferences, instanceOf, tariff preference scheme]
-
A.
preferential trade agreement
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.
tariff structure
A tariff structure is the organized schedule and framework of rates, rules, and conditions that determine how prices or charges are applied to specific goods, services, or usage levels.
-
C.
tariff liberalization instrument
chosen
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.
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.
tariff association
A tariff association is an organized group, often of businesses or carriers, that collaboratively develops, maintains, and publishes standardized rate schedules, rules, and conditions for services such as transportation or utilities.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.