Triple
T23777349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non-SDN Iran Sanctions Act List |
E587710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government sanctions list |
C45020
|
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 sanctions list Context triple: [Non-SDN Iran Sanctions Act List, instanceOf, U.S. government sanctions list]
-
A.
sanctions list
chosen
A sanctions list is an official register of individuals, entities, or countries subject to legal or regulatory restrictions, such as asset freezes or trade prohibitions, imposed by governments or international bodies.
-
B.
U.S. government trade control list
A U.S. government trade control list is an official compilation of specific items, technologies, services, or entities whose export, reexport, transfer, or dealings are restricted or regulated for reasons such as national security, foreign policy, or nonproliferation.
-
C.
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.
-
D.
federal government list
A federal government list is an official, organized compilation of entities, items, or information maintained by a national government for regulatory, administrative, or informational purposes.
-
E.
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.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:16 p.m.