Triple
T2540835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Association |
E56379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | instrument of economic coercion |
C2374
|
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: instrument of economic coercion Context triple: [Continental Association, instanceOf, instrument of economic coercion]
-
A.
economic blockade policy
chosen
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.
-
B.
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.
-
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.
instrument of state terror
An instrument of state terror is any tool, policy, institution, or practice deliberately used by a government to instill fear, suppress dissent, and maintain control through intimidation and violence.
-
E.
wartime economic control law
A wartime economic control law is a legal framework that grants governments special powers during armed conflict to regulate, direct, and restrict economic activities, resources, and markets in support of national defense and war objectives.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:47 p.m.