Triple
T12427693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holkar State of Indore |
E296940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maratha-ruled state |
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-ruled state Context triple: [Holkar State of Indore, instanceOf, Maratha-ruled state]
-
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.
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.
-
C.
office in the Maratha Empire
An office in the Maratha Empire was an administrative or military position within the Maratha governance structure, responsible for managing specific territorial, fiscal, or command duties under the authority of the Maratha rulers.
-
D.
Maratha nobility
Maratha nobility refers to the hereditary warrior-aristocratic class of the Maratha polity in early modern India, who held land, military authority, and administrative power under the Maratha Empire and its successor states.
-
E.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.