Triple

T2429127
Position Surface form Disambiguated ID Type / Status
Subject Battle of Heraclea E52800 entity
Predicate approximateEpiroteCasualties P6773 FINISHED
Object around 4,000 killed 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: around 4,000 killed | Statement: [Battle of Heraclea, approximateEpiroteCasualties, around 4,000 killed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateEpiroteCasualties
Context triple: [Battle of Heraclea, approximateEpiroteCasualties, around 4,000 killed]
  • A. casualtiesEstimate
    Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
  • B. militaryCasualtiesEstimate chosen
    Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
  • C. estimatedRomanForces
    Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
  • D. estimatedCarthaginianForces
    Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
  • E. plannedCasualtyExpectations
    Indicates that an entity has estimated or anticipated the number or extent of casualties expected to result from a planned action or event.
  • 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_69ab4959bcc0819083246f9fb10439e3 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abcc74a5108190a3a9631b0cc1a127 completed March 7, 2026, 6:57 a.m.
PD Predicate disambiguation batch_69abc5aa1b60819081b87f7985c6cff3 completed March 7, 2026, 6:28 a.m.
Created at: March 6, 2026, 9:43 p.m.