Triple

T14739789
Position Surface form Disambiguated ID Type / Status
Subject Battle of Karnal (1739) E346313 entity
Predicate casualtiesMughal P10775 FINISHED
Object tens of thousands 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: tens of thousands killed or wounded | Statement: [Battle of Karnal (1739), casualtiesMughal, tens of thousands killed or wounded]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesMughal
Context triple: [Battle of Karnal (1739), casualtiesMughal, tens of thousands killed or wounded]
  • A. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • B. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • C. primaryCasualtiesFrom
    Indicates that an entity is the main source or cause of the casualties experienced by another entity.
  • D. casualtiesDescription chosen
    Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
  • E. casualtiesAssociatedWithEvent
    Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
  • 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_69d822e6f1c88190bc494d491a907114 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7345680819093e901233a064e48 completed April 14, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69de8bf9331481909582045cd567d91f completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:29 a.m.