Triple

T14451360
Position Surface form Disambiguated ID Type / Status
Subject Hemu E358343 entity
Predicate outcomeOfSecondBattleOfPanipat P19109 FINISHED
Object defeat and capture by the Mughals 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: defeat and capture by the Mughals | Statement: [Hemu, outcomeOfSecondBattleOfPanipat, defeat and capture by the Mughals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: outcomeOfSecondBattleOfPanipat
Context triple: [Hemu, outcomeOfSecondBattleOfPanipat, defeat and capture by the Mughals]
  • A. sideInBattleOfBuxar
    Indicates being a participating side or party in the Battle of Buxar.
  • B. successorAsNawabOfAwadh
    Indicates that one entity became the next Nawab of Awadh, directly succeeding another in that position.
  • C. lastIndependentNawab
    Indicates that the subject is the final ruler to hold the title of independent Nawab before the position lost its autonomy or was abolished.
  • D. resultOfBattle chosen
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • E. afterConquestBy
    Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de916244948190bb09d1bfc485ba50 completed April 14, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69de5c3a02fc819097373f97a260cdeb completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:19 a.m.