Triple
T35630229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathore principalities in Marwar |
E1029562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rajput-ruled state |
C32665
|
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: Rajput-ruled state Context triple: [Rathore principalities in Marwar, instanceOf, Rajput-ruled state]
-
A.
Rajput princely state
chosen
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.
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.
-
C.
Rajput ruler
A Rajput ruler is a hereditary monarch or chieftain from the Rajput warrior clans of the Indian subcontinent, traditionally upholding codes of valor, honor, and patronage over their territories and subjects.
-
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.
Indian princely ruler
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.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.