Triple
T36766136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayuravarma |
E908343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kadamba king |
C62339
|
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: Kadamba king Context triple: [Mayuravarma, instanceOf, Kadamba king]
-
A.
Kadamba ruler
chosen
A Kadamba ruler is a monarch from the ancient Kadamba dynasty of South India, known for establishing one of the earliest native Kannada-speaking kingdoms and contributing to regional political, cultural, and architectural development.
-
B.
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.
-
C.
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.
-
D.
Chaulukya king
A Chaulukya king is a sovereign ruler from the Chaulukya (Solanki) dynasty that governed parts of western India, particularly Gujarat and Rajasthan, between the 10th and 13th centuries CE.
-
E.
Hoysala king
A Hoysala king is a medieval South Indian monarch from the Hoysala dynasty who ruled parts of present-day Karnataka, overseeing military campaigns, temple-centered patronage of art and architecture, and regional administration between the 10th and 14th centuries.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.