Triple
T11628222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhat family |
E276328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary Peshwa lineage |
C11070
|
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: hereditary Peshwa lineage Context triple: [Bhat family, instanceOf, hereditary Peshwa lineage]
-
A.
Hindu royal lineage
A Hindu royal lineage is a hereditary line of rulers and nobles within Hindu society, traditionally legitimized by sacred texts, divine ancestry, and ritual authority.
-
B.
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.
-
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.
office in the Maratha Empire
chosen
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.
-
E.
Maratha general
A Maratha general is a high-ranking military leader in the Maratha Empire responsible for planning and commanding campaigns, managing troops, and executing the strategic objectives of Maratha rulers.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.