Triple
T29610980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwar-Bharatpur union |
E754718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-independence Indian union of princely states |
C11265
|
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: post-independence Indian union of princely states Context triple: [Alwar-Bharatpur union, instanceOf, post-independence Indian union of princely states]
-
A.
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.
-
B.
division of British India
A division of British India was an administrative subdivision of a province, grouping several districts under a divisional commissioner for more efficient colonial governance and control.
-
C.
former state of India
chosen
A former state of India is a political and administrative unit that once existed within the Republic of India but was later dissolved, merged, renamed, or reorganized into one or more different states or union territories.
-
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.
state of India
A state of India is a primary administrative and political subdivision of the country, each with its own government, legislature, and defined territorial boundaries under the Indian Constitution.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:28 p.m.