Triple

T4734237
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cer E105084 entity
Predicate casualtiesAndLossesAustriaHungary P22214 FINISHED
Object over 6,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: over 6,000 killed | Statement: [Battle of Cer, casualtiesAndLossesAustriaHungary, over 6,000 killed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesAndLossesAustriaHungary
Context triple: [Battle of Cer, casualtiesAndLossesAustriaHungary, over 6,000 killed]
  • A. AustrianCasualtiesApprox chosen
    Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
  • B. casualtiesInflictedOn
    Indicates that one party has caused deaths or injuries to another party as a result of a harmful event or action.
  • C. englishCasualtiesKilledAndWounded
    Indicates the number of English individuals who were either killed or wounded as a result of a particular event or conflict.
  • D. casualtiesUnion
    Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6467a1fc819089485b4d76e0edc4 completed March 20, 2026, 3:14 p.m.
PD Predicate disambiguation batch_69bd6221c3b881908604f35f8de6f16b completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:19 p.m.