Triple

T1263478
Position Surface form Disambiguated ID Type / Status
Subject Battle of Oudenarde E12550 entity
Predicate casualtiesAlliance P17247 FINISHED
Object around 3,000 to 4,000 killed or 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: around 3,000 to 4,000 killed or wounded | Statement: [Battle of Oudenarde, casualtiesAlliance, around 3,000 to 4,000 killed or wounded]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesAlliance
Context triple: [Battle of Oudenarde, casualtiesAlliance, around 3,000 to 4,000 killed or wounded]
  • A. casualtiesAllied chosen
    Indicates the number or extent of losses (killed, wounded, or missing) suffered by allied forces in a conflict or incident.
  • B. casualtiesUnitedStates
    Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
  • C. casualtiesKilledUS
    Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
  • D. troopStrengthAlliedApprox
    Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
  • E. alliedUnit
    Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
  • 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_69a4933352e08190ac617291985e76c0 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4bfc8d6908190a5b2cf1051cc6d5e completed March 1, 2026, 10:38 p.m.
PD Predicate disambiguation batch_69a4bb7058e88190825b0cba5ee60b51 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:50 p.m.