Triple
T34919393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharajas of Jaipur |
E1007094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian princely rulers |
C35797
|
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: Indian princely rulers Context triple: [Maharajas of Jaipur, instanceOf, Indian princely rulers]
-
A.
Indian princely ruler
chosen
An Indian princely ruler is a hereditary monarch or sovereign of a semi-autonomous princely state in the Indian subcontinent who exercised varying degrees of internal authority under overarching imperial or colonial powers.
-
B.
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.
-
C.
Indian royal dynasty
An Indian royal dynasty is a hereditary ruling family or lineage that governed a specific region or kingdom in the Indian subcontinent, often characterized by distinct cultural, political, and architectural legacies.
-
D.
Rajput polity
Rajput polity refers to the decentralized, kinship-based systems of rule established by Rajput lineages in early medieval and medieval India, characterized by warrior aristocracy, clan honor, and negotiated sovereignty with larger imperial powers.
-
E.
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.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.