Triple

T3763243
Position Surface form Disambiguated ID Type / Status
Subject Kumanovo Agreement E82610 entity
Predicate typeOfCeasefire P50821 FINISHED
Object military-technical agreement 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: military-technical agreement | Statement: [Kumanovo Agreement, typeOfCeasefire, military-technical agreement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfCeasefire
Context triple: [Kumanovo Agreement, typeOfCeasefire, military-technical agreement]
  • A. hasCeasefire
    Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
  • B. calledCeasefire
    Indicates that an agreement has been made to temporarily stop hostilities or fighting between the involved parties.
  • C. ceasefireDeclared
    Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
  • D. ceasefireResolution
    Indicates a formal decision or agreement to halt hostilities or armed conflict between opposing parties, typically under specified terms and conditions.
  • 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. 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_69ad8b207b0081909d2b48843fbd8795 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcbfbecf8819099d80af480cbe2d2 completed March 8, 2026, 7:20 p.m.
PD Predicate disambiguation batch_69adc04c851c8190ae5eaebf36df539b completed March 8, 2026, 6:30 p.m.
PDg Predicate description generation batch_69adc0fe3e3c8190bd886c7745c172a0 completed March 8, 2026, 6:33 p.m.
Created at: March 8, 2026, 3:35 p.m.