Triple
T36596459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnitsky Act |
E902815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights 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: human rights sanctions regime Context triple: [Magnitsky Act, instanceOf, human rights sanctions regime]
-
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.
United Nations human rights review mechanism
A United Nations human rights review mechanism is a formal, periodic process through which UN bodies assess and monitor states’ compliance with international human rights obligations, typically involving state reports, independent expert or peer review, and public recommendations for improvement.
-
C.
human rights mandate
A human rights mandate is an authoritative directive or framework that obliges institutions, governments, or organizations to respect, protect, and promote fundamental human rights in their policies, practices, and decision-making.
-
D.
human rights resolution
A human rights resolution is a formal, collectively agreed statement or decision by a governing or international body that addresses, condemns, or prescribes actions regarding human rights issues and standards.
-
E.
human rights archive
A human rights archive is a curated collection of documents, testimonies, media, and other records that preserve, document, and provide evidence of human rights abuses and advocacy efforts over time.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.