Triple
T5561747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Entity List |
E145781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government trade-restriction tool |
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: U.S. government trade-restriction tool Context triple: [U.S. Entity List, instanceOf, U.S. government trade-restriction tool]
-
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.
economic blockade policy
An economic blockade policy is a state-led strategy that restricts or cuts off trade, financial transactions, and other economic interactions with a target nation or entity to exert political pressure or compel behavioral change.
-
C.
economic policy coordination tool
An economic policy coordination tool is a system that helps governments and institutions design, align, and monitor fiscal, monetary, and regulatory policies to achieve shared macroeconomic 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.