Triple

T2532685
Position Surface form Disambiguated ID Type / Status
Subject Battle of Aughrim (1691) E56196 entity
Predicate WilliamiteCasualties P35438 FINISHED
Object approximately 3,000 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: approximately 3,000 killed and wounded | Statement: [Battle of Aughrim (1691), WilliamiteCasualties, approximately 3,000 killed and wounded]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: WilliamiteCasualties
Context triple: [Battle of Aughrim (1691), WilliamiteCasualties, approximately 3,000 killed and wounded]
  • A. RoyalistArmyOutcome
    Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
  • B. englishCasualtiesKilledAndWounded
    Indicates the number of English individuals who were either killed or wounded as a result of a particular event or conflict.
  • C. casualtiesAssociatedWithEvent chosen
    Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
  • D. coalitionCasualties
    Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
  • E. BoerCasualties
    Indicates the number or occurrence of casualties suffered by Boer forces in a conflict or engagement.
  • 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_69ab4a49b6508190bc467fbef4bac334 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd279cf108190b03fb6e0265f39d9 completed March 7, 2026, 7:23 a.m.
PD Predicate disambiguation batch_69abd0c2e34c8190a914d5c2afba147c completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:47 p.m.