Triple
T36890549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikramaditya VI |
E911734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Chalukya emperor |
C55434
|
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: Western Chalukya emperor Context triple: [Vikramaditya VI, instanceOf, Western Chalukya 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.
Rashtrakuta emperor
A Rashtrakuta emperor was a sovereign ruler of the powerful Rashtrakuta dynasty that dominated large parts of the Indian subcontinent between the 8th and 10th centuries CE, overseeing military expansion, administration, and cultural patronage.
-
C.
Chalukya ruler
chosen
A Chalukya ruler is a monarch from the Chalukya dynasty that governed parts of the Indian subcontinent between the 6th and 12th centuries, overseeing administration, warfare, and patronage of art and architecture.
-
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.
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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.