Triple

T29009224
Position Surface form Disambiguated ID Type / Status
Subject Bishkek Protocol E736516 entity
Predicate ceasefireLineKnownAs P90746 FINISHED
Object Line of Contact in Nagorno-Karabakh 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: Line of Contact in Nagorno-Karabakh | Statement: [Bishkek Protocol, ceasefireLineKnownAs, Line of Contact in Nagorno-Karabakh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ceasefireLineKnownAs
Context triple: [Bishkek Protocol, ceasefireLineKnownAs, Line of Contact in Nagorno-Karabakh]
  • A. ceasefireLine chosen
    Indicates a demarcation line between opposing parties where active hostilities are formally suspended under a ceasefire agreement.
  • B. ceasefireDeclared
    Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
  • C. ceasefireSignedBy
    Indicates that a formal ceasefire agreement has been signed by the specified party or parties.
  • D. ceasefireBrokeredBy
    Indicates that a ceasefire agreement was arranged or facilitated through the mediation efforts of a specific party or entity.
  • E. ceasefireProvision
    Indicates a relationship where an agreement or arrangement includes specific terms or conditions governing a ceasefire between parties in conflict.
  • 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_69f077eb81e88190ad9ff62cbb9f555e completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f6617ba4a88190bfc5c305acb4f93f completed May 2, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69f660f082508190a95a7888ad66cb2e completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 9:40 a.m.