Triple
T19483070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson–Vanik amendment |
E487440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade restriction |
C19220
|
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 restriction Context triple: [Jackson–Vanik amendment, instanceOf, trade restriction]
-
A.
trade embargo
A trade embargo is a government-imposed restriction that partially or completely prohibits commercial exchange of goods and services with a specific country, group, or entity for political, economic, or security reasons.
-
B.
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.
-
C.
tax barrier
A tax barrier is a fiscal measure, such as tariffs, duties, or restrictive tax rules, that impedes or discourages cross-border trade, investment, or economic activity.
-
D.
U.S. government trade-restriction tool
chosen
A U.S. government trade-restriction tool is a legal or regulatory mechanism—such as tariffs, sanctions, export controls, or import quotas—used to limit, condition, or prohibit cross-border commerce in order to advance national security, economic, or foreign policy objectives.
-
E.
sanctions regime
A sanctions regime is a structured set of legal and policy measures—such as trade restrictions, asset freezes, and travel bans—imposed by one or more actors to coerce, deter, or punish targeted states, entities, or individuals.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.