Triple
T36186127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukumtar-ud-Daula |
E1046849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hyderabad State nobility |
C63948
|
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: Hyderabad State nobility Context triple: [Mukumtar-ud-Daula, instanceOf, Hyderabad State nobility]
-
A.
Nizam of Hyderabad
The Nizam of Hyderabad was the hereditary monarch and ruler of the princely state of Hyderabad in south-central India, known for immense wealth, semi-autonomous governance under British suzerainty, and a significant role in regional politics until the state's integration into the Indian Union in 1948.
-
B.
Vijayanagara noble
A Vijayanagara noble was a high-ranking aristocrat in the Vijayanagara Empire who held land grants, military or administrative authority, and courtly status while serving the king in governance, warfare, and regional control.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.