Triple
T7925475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 1267 |
E184049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sanctions regime |
C23186
|
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: sanctions regime Context triple: [UN Security Council Resolution 1267, instanceOf, sanctions regime]
-
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.
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.
-
D.
arms deal
An arms deal is a transaction involving the sale, transfer, or exchange of weapons and military equipment between parties, often states, organizations, or private entities.
-
E.
anti–money laundering measure
An anti–money laundering measure is a policy, procedure, or control designed to detect, prevent, and report the concealment of illicitly obtained funds within the legitimate financial system.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:06 p.m.