Triple
T23302214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jethwa Rajput chiefdoms |
E590333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rajput chiefdoms |
C1186
|
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: Rajput chiefdoms Context triple: [Jethwa Rajput chiefdoms, instanceOf, Rajput chiefdoms]
-
A.
Rajput princely state
A Rajput princely state was a semi-autonomous, monarch-ruled territory in the Indian subcontinent governed by a Rajput dynasty under the suzerainty of larger empires such as the Mughals or the British Crown.
-
B.
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.
-
C.
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.
-
D.
Rajput ruler
A Rajput ruler is a hereditary monarch or chieftain from the Rajput warrior clans of the Indian subcontinent, traditionally upholding codes of valor, honor, and patronage over their territories and subjects.
-
E.
chiefdoms
chosen
Chiefdoms are hierarchical political organizations in which a central leader (chief) holds authority over multiple communities, redistributing resources and managing social, economic, and religious affairs.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:04 p.m.