Triple
T37086608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanderao Holkar |
E918303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Holkar dynasty |
C46891
|
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: member of the Holkar dynasty Context triple: [Khanderao Holkar, instanceOf, member of the Holkar dynasty]
-
A.
member of Holkar dynasty
chosen
A member of the Holkar dynasty is an individual belonging to the Maratha royal family that ruled the princely state of Indore and surrounding regions in central India from the 18th to mid-20th century.
-
B.
member of the Bhonsle dynasty
A member of the Bhonsle dynasty is an individual belonging to the Maratha royal lineage that rose to prominence in western India, notably through leaders like Shivaji who founded the Maratha Empire.
-
C.
Asaf Jahi dynasty member
A member of the Asaf Jahi dynasty is an individual belonging to the royal family that ruled the princely state of Hyderabad in India from the early 18th to the mid-20th century.
-
D.
member of the Adil Shahi dynasty
A member of the Adil Shahi dynasty is an individual belonging to the Turkic-origin royal family that ruled the Bijapur Sultanate in the Deccan region of India from the late 15th to the late 17th century.
-
E.
member of the Peshwa family
A member of the Peshwa family is an individual belonging by birth or marriage to the influential Brahmin dynasty that served as hereditary prime ministers and de facto leaders of the Maratha Empire in 18th-century India.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.