Triple

T23091958
Position Surface form Disambiguated ID Type / Status
Subject Battle of Hlobane E575776 entity
Predicate ZuluCasualties P150892 FINISHED
Object substantial but lower than British and allies 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: substantial but lower than British and allies | Statement: [Battle of Hlobane, ZuluCasualties, substantial but lower than British and allies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ZuluCasualties
Context triple: [Battle of Hlobane, ZuluCasualties, substantial but lower than British and allies]
  • A. BoerCasualties
    Indicates the number or occurrence of casualties suffered by Boer forces in a conflict or engagement.
  • B. battleCommanderOnZuluSide
    Indicates that the subject served as a commanding officer for the Zulu forces in a specific battle.
  • C. battleCasualty
    Indicates that an entity was killed, wounded, or otherwise harmed as a direct result of a specific battle or armed conflict.
  • D. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • E. UnionCasualtiesKilledAndWounded
    Indicates the number of Union forces who were either killed or wounded as a result of a specific military engagement or event.
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18daa68d48190842e9cb6de31ea79 completed April 29, 2026, 4:48 a.m.
PD Predicate disambiguation batch_69ef89e5ce748190b2c3ac3843484127 completed April 27, 2026, 4:08 p.m.
PDg Predicate description generation batch_69ef9b7494f4819088ae59ea3d0ae8ab completed April 27, 2026, 5:23 p.m.
Created at: April 17, 2026, 3:57 p.m.