Triple

T30977109
Position Surface form Disambiguated ID Type / Status
Subject UN Security Council Resolution 1506 E789260 entity
Predicate sanctionsLifted P170869 FINISHED
Object aviation ban 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: aviation ban on Libya | Statement: [UN Security Council Resolution 1506, sanctionsLifted, aviation ban on Libya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sanctionsLifted
Context triple: [UN Security Council Resolution 1506, sanctionsLifted, aviation ban on Libya]
  • A. conditionsLiftingOfSanctionsOn
    Indicates that one entity specifies or determines the requirements under which sanctions imposed on another entity will be removed or relaxed.
  • B. appliedSanctionsTo
    Indicates that one entity has imposed sanctions or punitive restrictions on another entity.
  • C. imposesSanctionsOn
    Indicates that one entity enforces punitive or restrictive measures against another entity, typically to influence or penalize its behavior.
  • D. mutualExcommunicationsLifted
    Indicates that previously established excommunications between two parties have been officially revoked by both sides.
  • E. sanctionsTarget
    Indicates that an entity imposes sanctions or punitive measures against another entity as its target.
  • 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_69f224c4831c8190be53924ec25a150a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f695f9fe7c819084322bf6cdc70a13 completed May 3, 2026, 12:25 a.m.
PD Predicate disambiguation batch_69f690ef92308190903a54fc74233269 completed May 3, 2026, 12:03 a.m.
PDg Predicate description generation batch_69f695385a2881908cc28ef97fffc867 completed May 3, 2026, 12:22 a.m.
Created at: April 29, 2026, 8:55 p.m.