Triple

T16298672
Position Surface form Disambiguated ID Type / Status
Subject UN Security Council Resolution 669 E395718 entity
Predicate typeOfSanctionsAddressed P18137 FINISHED
Object economic sanctions 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: economic sanctions | Statement: [UN Security Council Resolution 669, typeOfSanctionsAddressed, economic sanctions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfSanctionsAddressed
Context triple: [UN Security Council Resolution 669, typeOfSanctionsAddressed, economic sanctions]
  • A. typeOfSanction chosen
    Indicates the specific category or kind of sanction that is applied in a given situation.
  • B. coSanctions
    Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
  • C. coSanctionsWith
    Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
  • D. countrySubjectToSanctions
    Indicates that a country is currently facing formal sanctions or restrictive measures imposed by another state or international body.
  • E. isSanctionedBy
    Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
  • 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_69d87f23bb088190a16fbb91a1957ea5 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e25e30ee288190b78807b60cb18e22 completed April 17, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69e219fa5508819097e9d383348bf174 completed April 17, 2026, 11:31 a.m.
Created at: April 10, 2026, 5:06 a.m.