Triple
T14451494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akbar–Rajput alliance |
E358347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal–Rajput relations |
C34785
|
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–Rajput relations Context triple: [Akbar–Rajput alliance, instanceOf, Mughal–Rajput relations]
-
A.
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.
-
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.
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.
-
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.
Maratha fiscal levy
A Maratha fiscal levy is a tax or tribute imposed by the Maratha state on agrarian produce, trade, or territories under its influence, serving as a key instrument of revenue extraction and political control.
- F. None of above. chosen
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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.