Triple

T19018292
Position Surface form Disambiguated ID Type / Status
Subject Mughal–Sikh conflicts E465414 entity
Predicate hasPart P35 FINISHED
Object Battle of Sialkot (1702) NE NERFINISHED

How this triple was built (3 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: Battle of Sialkot (1702) | Statement: [Mughal–Sikh conflicts, hasPart, Battle of Sialkot (1702)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Battle of Sialkot (1702)
Context triple: [Mughal–Sikh conflicts, hasPart, Battle of Sialkot (1702)]
  • A. Battle of Lahore (1759)
    The Battle of Lahore (1759) was a key 18th-century clash in which Ahmad Shah Durrani’s Afghan forces checked Maratha expansion in the Punjab region, shaping the balance of power in northern India.
  • B. Battle of Amritsar (1709)
    The Battle of Amritsar (1709) was an early 18th-century clash in Punjab between Sikh forces and the Mughal Empire that marked a significant step in the Sikhs’ armed resistance and consolidation of power.
  • C. Battle of Karnal (1739)
    The Battle of Karnal (1739) was a decisive confrontation in which Persian ruler Nader Shah crushed the Mughal Empire’s forces, leading to the sack of Delhi and marking a major step in the empire’s decline.
  • D. Battle of Sirhind (1764)
    The Battle of Sirhind (1764) was a decisive engagement in which Sikh forces defeated the Mughal governor of Sirhind, leading to Sikh control over the region and a major decline in Mughal authority in Punjab.
  • E. Battle of Murchehkhort (1729)
    The Battle of Murchehkhort (1729) was a decisive victory by Nader Shah that helped secure his dominance in Iran and paved the way for the eventual establishment of the Afsharid dynasty.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Battle of Sialkot (1702)
Target entity description: The Battle of Sialkot (1702) was an early 18th-century clash between Mughal forces and the Sikhs near Sialkot in Punjab, forming part of the protracted Mughal–Sikh military struggle.
  • A. Battle of Lahore (1759)
    The Battle of Lahore (1759) was a key 18th-century clash in which Ahmad Shah Durrani’s Afghan forces checked Maratha expansion in the Punjab region, shaping the balance of power in northern India.
  • B. Battle of Amritsar (1709)
    The Battle of Amritsar (1709) was an early 18th-century clash in Punjab between Sikh forces and the Mughal Empire that marked a significant step in the Sikhs’ armed resistance and consolidation of power.
  • C. Battle of Karnal (1739)
    The Battle of Karnal (1739) was a decisive confrontation in which Persian ruler Nader Shah crushed the Mughal Empire’s forces, leading to the sack of Delhi and marking a major step in the empire’s decline.
  • D. Battle of Sirhind (1764)
    The Battle of Sirhind (1764) was a decisive engagement in which Sikh forces defeated the Mughal governor of Sirhind, leading to Sikh control over the region and a major decline in Mughal authority in Punjab.
  • E. Battle of Murchehkhort (1729)
    The Battle of Murchehkhort (1729) was a decisive victory by Nader Shah that helped secure his dominance in Iran and paved the way for the eventual establishment of the Afsharid dynasty.
  • F. None of above. chosen

Provenance (2 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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6dd0e6c8190a6dc6af1f7901299 completed April 20, 2026, 7:33 a.m.
Created at: April 10, 2026, 12:02 p.m.