Triple

T29384748
Position Surface form Disambiguated ID Type / Status
Subject United Nations Security Council Resolution 2009 E745220 entity
Predicate eases P68009 FINISHED
Object certain sanctions on Libya 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: certain sanctions on Libya | Statement: [United Nations Security Council Resolution 2009, eases, certain sanctions on Libya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eases
Context triple: [United Nations Security Council Resolution 2009, eases, certain sanctions on Libya]
  • A. relie
    Indicates that one entity provides relief, comfort, or alleviation from distress, pain, or difficulty for another entity.
  • B. appeases
    Indicates an action where one entity calms, placates, or satisfies another entity to reduce anger, tension, or hostility.
  • C. relief chosen
    Indicates a state or action in which distress, pain, or difficulty is reduced, eased, or removed for an entity.
  • D. eve
    Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
  • E. erlässt
    Indicates that an authority issues, enacts, or promulgates something such as a law, decree, or regulation.
  • 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_69f0a79cfd5481909b4dde750cb8d2c6 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669d0c45c8190ac5b67a0e89e8aae completed May 2, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 2:37 p.m.