Triple

T37627153
Position Surface form Disambiguated ID Type / Status
Subject Battle of Blue Licks E936242 entity
Predicate casualtiesPatriot P45977 FINISHED
Object high proportion of force killed or 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: high proportion of force killed or captured | Statement: [Battle of Blue Licks, casualtiesPatriot, high proportion of force killed or captured]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesPatriot
Context triple: [Battle of Blue Licks, casualtiesPatriot, high proportion of force killed or captured]
  • A. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • B. PatriotCasualties chosen
    Indicates that the event involves casualties suffered by patriot forces or supporters.
  • C. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • D. UScasualties
    Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
  • E. casualtiesDescription
    Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
  • 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_69f76ed24820819081bafd36e9088701 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaa1321b48190af92a3e7ec24ec5b completed May 6, 2026, 8:52 p.m.
PD Predicate disambiguation batch_69fba8860f98819080b7bab05837b974 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:18 p.m.