Triple
T12853937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appa Sahib Bhonsle |
E307399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nagpur Bhonsle dynasty ruler |
C30464
|
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: Nagpur Bhonsle dynasty ruler Context triple: [Appa Sahib Bhonsle, instanceOf, Nagpur Bhonsle dynasty ruler]
-
A.
ruler of Indore
The ruler of Indore is the sovereign or governing authority who historically held political power and administrative control over the princely state or region of Indore.
-
B.
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.
-
C.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
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 nobility
chosen
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.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:37 p.m.