Triple
T36596492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnitsky Act |
E902815
|
entity |
| Predicate | sanctionsTool |
P125755
|
FINISHED |
| Object | asset blocking |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: asset blocking | Statement: [Magnitsky Act, sanctionsTool, asset blocking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionsTool Context triple: [Magnitsky Act, sanctionsTool, asset blocking]
-
A.
coSanctions
Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
-
B.
appliedSanctionsTo
Indicates that one entity has imposed sanctions or punitive restrictions on another entity.
-
C.
relatedSanctions
chosen
Indicates that there is an association between an entity and one or more sanctions, such as penalties, restrictions, or punitive measures applied in connection with that entity.
-
D.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
-
E.
countrySubjectToSanctions
Indicates that a country is currently facing formal sanctions or restrictive measures imposed by another state or international body.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.