Triple

T9651504
Position Surface form Disambiguated ID Type / Status
Subject Battle of Maiwand E233344 entity
Predicate casualtiesAndLossesAfghan P40994 FINISHED
Object several thousand killed and wounded 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: several thousand killed and wounded | Statement: [Battle of Maiwand, casualtiesAndLossesAfghan, several thousand killed and wounded]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesAndLossesAfghan
Context triple: [Battle of Maiwand, casualtiesAndLossesAfghan, several thousand killed and wounded]
  • A. AfghanCasualties chosen
    Indicates the number or occurrence of casualties suffered by Afghan individuals or forces in a given event or context.
  • B. casualtiesDescription
    Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
  • C. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • D. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • E. casualtiesTotal
    Indicates the total number of people killed and injured as a result of a particular event or incident.
  • 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_69ca848b31648190b57aa55da20285be completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9bb0cce88190b7eacc8b43450d7f completed April 1, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69ccd5b0263081908cf6df3eb07d71b0 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:13 p.m.