Triple
T34699619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratan Singh I |
E1000329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Monarch of Mewar |
C30631
|
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: Monarch of Mewar Context triple: [Ratan Singh I, instanceOf, Monarch of Mewar]
-
A.
King of Mewar
chosen
The King of Mewar is the sovereign ruler of the historic Mewar region, traditionally responsible for governance, military leadership, cultural patronage, and the protection of Rajput honor and heritage.
-
B.
Maharaja
A Maharaja is a hereditary Indian monarch or high-ranking noble, traditionally ruling over a princely state with significant political, military, and cultural authority.
-
C.
Raja-guru
Raja-guru is a royal spiritual preceptor who advises the king on religious, ethical, and philosophical matters, guiding governance according to sacred principles.
-
D.
Maitraka king
A Maitraka king is a ruler from the Maitraka dynasty (c. 475–776 CE) that governed the region of Saurashtra and parts of Gujarat in western India, known for their patronage of Buddhism, Jainism, and Hinduism and for maintaining regional power after the decline of the Gupta Empire.
-
E.
Nayak ruler
A Nayak ruler is a sovereign or regional governor from the Nayak dynasty who governed parts of South India, particularly during the post-Vijayanagara period, known for their patronage of art, architecture, and regional administration.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.