Triple

T4175076
Position Surface form Disambiguated ID Type / Status
Subject Battle of Bergen E86455 entity
Predicate AlliedCasualtiesAndLosses P17247 FINISHED
Object about 2,500 killed, wounded and captured 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: about 2,500 killed, wounded and captured | Statement: [Battle of Bergen, AlliedCasualtiesAndLosses, about 2,500 killed, wounded and captured]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AlliedCasualtiesAndLosses
Context triple: [Battle of Bergen, AlliedCasualtiesAndLosses, about 2,500 killed, wounded and captured]
  • A. casualtiesAllied chosen
    Indicates the number or extent of losses (killed, wounded, or missing) suffered by allied forces in a conflict or incident.
  • B. UScasualties
    Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
  • C. casualtiesUnion
    Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
  • D. NATOcasualtiesMilitaryKilled
    Indicates that members of NATO military forces were killed as casualties.
  • E. englishCasualtiesKilledAndWounded
    Indicates the number of English individuals who were either killed or wounded as a result of a particular event 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af07078cb081909f64326b12522410 completed March 9, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69af019155448190b19868583272513f completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:45 p.m.