Triple

T16254288
Position Surface form Disambiguated ID Type / Status
Subject Siege of Bijapur (1685–1686) E394589 entity
Predicate instanceOf P0 FINISHED
Object event in the Mughal–Adil Shahi conflicts C14416 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: event in the Mughal–Adil Shahi conflicts
Context triple: [Siege of Bijapur (1685–1686), instanceOf, event in the Mughal–Adil Shahi conflicts]
  • A. event in the Third Anglo-Mysore War
    An event in the Third Anglo-Mysore War is a specific military, political, or diplomatic occurrence between 1789 and 1792 that significantly influenced the course or outcome of the conflict between the Kingdom of Mysore and the British East India Company and its allies.
  • B. Mughal campaign chosen
    A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
  • C. Anglo-Maratha War
    The Anglo-Maratha War refers to a series of three late 18th- and early 19th-century conflicts between the British East India Company and the Maratha Empire that ultimately led to British dominance over most of India.
  • D. Mughal–Rajput relations
    Mughal–Rajput relations refer to the complex web of political alliances, military conflicts, matrimonial ties, and cultural exchanges between the Mughal Empire and the Rajput kingdoms of northern and western India from the 16th to 18th centuries.
  • E. event in the Byzantine–Ottoman wars
    An "event in the Byzantine–Ottoman wars" is a specific historical occurrence—such as a battle, siege, treaty, or political development—that took place within the broader series of conflicts between the Byzantine Empire and the Ottoman state.
  • F. None of above.

Provenance (1 batch)

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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
Created at: April 10, 2026, 5:04 a.m.