Triple
T7124178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Rajasthan princely states |
E166018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian princely states union |
C8966
|
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 states union Context triple: [Union of Rajasthan princely states, instanceOf, Indian princely states union]
-
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.
Sikh state
A Sikh state is a political entity in which governance, laws, and social institutions are significantly shaped by Sikh religious principles, history, and community leadership.
-
C.
confederation of states
chosen
A confederation of states is a union of sovereign states that voluntarily cooperate on certain common matters through a central body that has limited authority and depends on the member states for implementation and enforcement.
-
D.
union territory of India
A union territory of India is an administrative division directly governed by the Central Government of India, often with limited or partial state-like legislative powers.
-
E.
former state of India
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.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:44 p.m.