Triple
T26800768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhruva Dharavarsha |
E671093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rashtrakuta emperor |
C52052
|
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: Rashtrakuta emperor Context triple: [Dhruva Dharavarsha, instanceOf, Rashtrakuta emperor]
-
A.
Eastern Chalukya king
An Eastern Chalukya king is a monarch from the Eastern Chalukya dynasty who ruled parts of eastern Deccan, particularly in present-day Andhra Pradesh, overseeing administration, warfare, culture, and patronage of religion and the arts.
-
B.
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.
-
C.
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.
-
D.
Vemulavada Chalukya ruler
A Vemulavada Chalukya ruler is a monarch from the medieval South Indian Chalukya dynasty based at Vemulavada, known for regional governance, temple patronage, and participation in Deccan power politics.
-
E.
Chola emperor
A Chola emperor is the sovereign ruler of the medieval South Indian Chola dynasty, responsible for governing its territories, leading military campaigns, overseeing administration, and patronizing religion, art, and culture.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:22 a.m.