Triple

T37786394
Position Surface form Disambiguated ID Type / Status
Subject UNOMIG E941965 entity
Predicate terminatedByResolution P19807 FINISHED
Object United Nations Security Council Resolution 1866 NE NERFINISHED

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: United Nations Security Council Resolution 1866 | Statement: [UNOMIG, terminatedByResolution, United Nations Security Council Resolution 1866]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terminatedByResolution
Context triple: [UNOMIG, terminatedByResolution, United Nations Security Council Resolution 1866]
  • A. terminationEndedIn
    Indicates that a termination event concluded with a specific outcome or result.
  • B. resolvedIn chosen
    Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
  • C. followedByResolution
    Indicates that one event, state, or action is directly succeeded by a resolving event, state, or action in a sequence.
  • D. terminationResistance
    Indicates resistance or opposition to ending, stopping, or terminating a process, state, or relationship.
  • E. terminateIn
    Indicates that one entity ends, concludes, or comes to a stop within, at, or because of another entity or condition.
  • 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_69f76ee5cb0c81909a363d1c929156c0 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:19 p.m.