Triple
T38666784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maratha control of Bundelkhand |
E940474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maratha expansion |
C29654
|
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: Maratha expansion Context triple: [Maratha control of Bundelkhand, instanceOf, Maratha expansion]
-
A.
Maratha polity
chosen
Maratha polity refers to the decentralized, confederate political system of the Maratha Empire, characterized by a powerful but often contested central authority (the Chhatrapati and Peshwa) and semi-autonomous regional chiefs (sardars) who exercised significant military, fiscal, and administrative control.
-
B.
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.
-
C.
Mughal campaign
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.
-
D.
Maratha
Maratha refers to a prominent warrior and landowning community from western India, historically known for establishing the Maratha Empire and challenging Mughal rule in the 17th and 18th centuries.
-
E.
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.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.