Triple
T15703679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal conquest of Gujarat |
E380654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal expansion |
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: Mughal expansion Context triple: [Mughal conquest of Gujarat, instanceOf, Mughal expansion]
-
A.
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.
-
B.
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.
-
C.
Mughal administration
Mughal administration was a centralized imperial governance system in South Asia that combined Persian bureaucratic practices, a hierarchical mansabdari (rank) system, and regional autonomy to manage revenue, military, and justice across a diverse empire.
-
D.
subah of the Mughal Empire
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
-
E.
Maratha polity
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.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.