Triple
T13554610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Orders in Council of 1807 |
E323737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade restriction measure |
C19995
|
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 measure Context triple: [British Orders in Council of 1807, instanceOf, trade restriction measure]
-
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.
U.S. government trade-restriction tool
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.
-
C.
trade policy instrument
chosen
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.
-
D.
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.
-
E.
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.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:46 p.m.