Triple

T25563229
Position Surface form Disambiguated ID Type / Status
Subject Sarajevo ceasefire (January 1992) E640769 entity
Predicate belligerentInvolved P10155 FINISHED
Object Yugoslav People’s Army 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: Yugoslav People’s Army | Statement: [Sarajevo ceasefire (January 1992), belligerentInvolved, Yugoslav People’s Army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belligerentInvolved
Context triple: [Sarajevo ceasefire (January 1992), belligerentInvolved, Yugoslav People’s Army]
  • A. belligerentAgainst
    Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
  • B. belligerentFor
    Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
  • C. conflictBelligerent chosen
    Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
  • D. belligerentInterest
    Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
  • E. belligerentControl
    Indicates that one party exercises control, authority, or coercive influence over another in a hostile or conflict-oriented context.
  • 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_69e75dc1beb08190bac7d76b8d6e7bc4 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8fa9fa0819098761026a7f9353d completed May 2, 2026, 1:15 p.m.
PD Predicate disambiguation batch_69f480789be08190ab252a6de3797200 completed May 1, 2026, 10:29 a.m.
Created at: April 21, 2026, 3:47 p.m.