Triple
T9250331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 883 |
E222305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international sanctions measure |
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: international sanctions measure Context triple: [UN Security Council Resolution 883, instanceOf, international sanctions measure]
-
A.
sanctions regime
chosen
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.
-
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 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.
-
D.
international order
International order is the overarching system of rules, institutions, norms, and power relationships that structure how states and other global actors interact, cooperate, and compete.
-
E.
international trade dispute
An international trade dispute is a conflict between countries or trading entities over the interpretation, application, or alleged violation of trade agreements, policies, or practices affecting cross-border commerce.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:31 p.m.