Triple

T15786800
Position Surface form Disambiguated ID Type / Status
Subject Puntland–Somaliland conflict E382756 entity
Predicate hasCeasefireAttempts P22513 FINISHED
Object locally mediated truces 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: locally mediated truces | Statement: [Puntland–Somaliland conflict, hasCeasefireAttempts, locally mediated truces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCeasefireAttempts
Context triple: [Puntland–Somaliland conflict, hasCeasefireAttempts, locally mediated truces]
  • A. hasCeasefireAttempt chosen
    Indicates that an effort or initiative has been made to establish, negotiate, or implement a ceasefire between parties in conflict.
  • B. hasCeasefire
    Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
  • C. calledCeasefire
    Indicates that an agreement has been made to temporarily stop hostilities or fighting between the involved parties.
  • D. completionAttemptsBy
    Indicates that a specific entity’s completion attempts are attributed to or performed by another entity.
  • E. endedCeasefire
    Indicates that a previously established ceasefire between parties has been terminated or broken.
  • 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_69d86da16e188190b89af699f1ed0bfe completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0540380448190a025338f0e62e6d1 completed April 16, 2026, 3:14 a.m.
PD Predicate disambiguation batch_69e00537bd1c81908d6e832792fd934f completed April 15, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:48 a.m.