Triple

T10455674
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Little Bighorn E246545 entity
Predicate casualtiesNativeForces P47610 FINISHED
Object dozens 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: dozens killed and wounded | Statement: [Battle of the Little Bighorn, casualtiesNativeForces, dozens killed and wounded]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesNativeForces
Context triple: [Battle of the Little Bighorn, casualtiesNativeForces, dozens killed and wounded]
  • A. nativeCasualties chosen
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • B. militaryCasualtiesSide
    Indicates the side or party in a conflict to which the recorded military casualties belong.
  • C. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • D. primaryCasualtiesFrom
    Indicates that an entity is the main source or cause of the casualties experienced by another entity.
  • E. coalitionCasualties
    Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
  • 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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fe48d15c8190bae0d4859e6cda5d completed April 7, 2026, 12:53 p.m.
PD Predicate disambiguation batch_69d4fb7d353c8190a73f439a956c7606 completed April 7, 2026, 12:41 p.m.
Created at: April 6, 2026, 12:18 p.m.