Triple

T4870090
Position Surface form Disambiguated ID Type / Status
Subject Kharkiv counteroffensive (2022) E109064 entity
Predicate casualtiesNote P10775 FINISHED
Object exact casualty figures disputed 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: exact casualty figures disputed | Statement: [Kharkiv counteroffensive (2022), casualtiesNote, exact casualty figures disputed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesNote
Context triple: [Kharkiv counteroffensive (2022), casualtiesNote, exact casualty figures disputed]
  • A. casualtiesDescription chosen
    Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
  • B. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • C. casualtiesIncluded
    Indicates that the referenced count or report of casualties explicitly includes the specified individuals or groups.
  • D. casualtiesType
    Indicates the specific category or nature of casualties (e.g., killed, injured, missing) associated with an event or incident.
  • E. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ff981fc819080d4466c6fe06cf3 completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c28e56081908ee411ac94c3769e completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:27 p.m.