Triple
T36216995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vakpati Munja |
E1047725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Paramara king |
C65177
|
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: Paramara king Context triple: [Vakpati Munja, instanceOf, Paramara king]
-
A.
Yadava king
A Yadava king is a ruler belonging to the Yadava dynasty, historically associated with the Yadu lineage in ancient and medieval India, often linked to regions like Mathura and later the Deccan.
-
B.
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.
-
C.
Chandela king
A Chandela king is a ruler from the medieval Indian Chandela dynasty, known for governing central Indian regions like Bundelkhand and commissioning monumental Hindu and Jain temples such as those at Khajuraho.
-
D.
Raja of Marwar
The Raja of Marwar is the sovereign ruler of the Marwar region, historically centered in Jodhpur, responsible for governance, military leadership, and patronage of culture within this Rajput kingdom.
-
E.
Pandya king
A Pandya king is a monarch of the ancient South Indian Pandya dynasty, ruling over parts of present-day Tamil Nadu and known for patronage of trade, literature, and temple architecture.
- F. None of above. chosen
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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.