Triple
T21581896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specially Designated Nationals and Blocked Persons List |
E532542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: sanctions list Context triple: [Specially Designated Nationals and Blocked Persons List, instanceOf, sanctions list]
-
A.
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.
-
B.
aviation security list
An aviation security list is an official roster of individuals or entities identified as potential threats to civil aviation, used to screen and restrict their access to flights, airports, or related services.
-
C.
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.
-
D.
most wanted list
A most wanted list is an official compilation of individuals sought by authorities, typically for serious crimes, prioritized for capture or information leading to their arrest.
-
E.
passenger list
A passenger list is a documented record identifying all individuals traveling on a specific vehicle, vessel, or flight, often including personal and travel details for administrative, safety, and legal purposes.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:31 p.m.