Triple
T35993403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Hyderabad State |
E1040911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | princely state government |
C64826
|
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: princely state government Context triple: [Government of Hyderabad State, instanceOf, princely state government]
-
A.
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.
-
B.
government of an Indian state
The government of an Indian state is the political and administrative authority responsible for governing that state, comprising the Governor, the elected legislative assembly, and the council of ministers headed by the Chief Minister.
-
C.
group of princely states
A group of princely states is a collection of semi-autonomous, monarch-ruled territories historically bound together under a larger imperial or colonial framework for purposes of governance, diplomacy, or administration.
-
D.
princely state railway
A princely state railway is a railway system owned, financed, or operated by a semi-autonomous princely state under indirect colonial or imperial oversight, typically integrated to varying degrees with a larger national or imperial rail network.
-
E.
Jat-ruled state
A Jat-ruled state is a political entity or kingdom historically governed by rulers from the Jat community, typically characterized by agrarian-based power structures and regional autonomy in North India.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.