Triple

T30120573
Position Surface form Disambiguated ID Type / Status
Subject Council Decision 2016/446/CFSP E765551 entity
Predicate typeOfSanctionsInstrument P199539 FINISHED
Object CFSP decision establishing or amending restrictive measures 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: CFSP decision establishing or amending restrictive measures | Statement: [Council Decision 2016/446/CFSP, typeOfSanctionsInstrument, CFSP decision establishing or amending restrictive measures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfSanctionsInstrument
Context triple: [Council Decision 2016/446/CFSP, typeOfSanctionsInstrument, CFSP decision establishing or amending restrictive measures]
  • A. typeOfSanction
    Indicates the specific category or kind of sanction that is applied in a given situation.
  • B. typeOfSanctionsAuthority
    Indicates the authority or legal basis under which specific sanctions are imposed or administered.
  • C. mediaTypeOfSanctioningBody
    Indicates the type or category of media associated with the sanctioning body.
  • D. coSanctions
    Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
  • E. appliedSanctionsTo
    Indicates that one entity has imposed sanctions or punitive restrictions on another entity.
  • F. None of above. chosen

Provenance (4 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_69f2247716748190ae4f16998f49ddf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff41645c548190b7cb4e53079b93ef completed May 9, 2026, 2:15 p.m.
PD Predicate disambiguation batch_69ff410aa33c8190869ba769ac2a93ce completed May 9, 2026, 2:13 p.m.
PDg Predicate description generation batch_69ff4163a8548190b0eaafd0a377b141 completed May 9, 2026, 2:14 p.m.
Created at: April 29, 2026, 7:13 p.m.