Triple
T35715034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rao Chunda |
E1031979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rathore ruler |
C16554
|
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: Rathore ruler Context triple: [Rao Chunda, instanceOf, Rathore ruler]
-
A.
Rajput ruler
chosen
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.
-
B.
Gurjara-Pratihara ruler
A Gurjara-Pratihara ruler is a monarch from the early medieval North Indian Gurjara-Pratihara dynasty, known for resisting Arab invasions and patronizing art, architecture, and regional political consolidation between the 8th and 11th centuries.
-
C.
Kalhora dynasty ruler
A Kalhora dynasty ruler is a sovereign from the Kalhora family who governed Sindh (in present-day Pakistan) between the early 18th and late 18th centuries, overseeing its political, economic, and cultural affairs.
-
D.
Maitraka ruler
A Maitraka ruler is a monarch from the Maitraka dynasty that governed parts of western India, particularly Saurashtra and Gujarat, between the 5th and 8th centuries CE.
-
E.
Wadiyar dynasty ruler
A Wadiyar dynasty ruler is a monarch from the royal family that governed the Kingdom of Mysore, overseeing its political, cultural, and economic development across several centuries in southern India.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.