Triple
T25959552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubja Vishnuvardhana I |
E645498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Chalukya king |
C50158
|
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: Eastern Chalukya king Context triple: [Kubja Vishnuvardhana I, instanceOf, Eastern Chalukya king]
-
A.
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.
-
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.
Kakatiya ruler
A Kakatiya ruler is a monarch from the medieval Kakatiya dynasty of South India, known for consolidating regional power, promoting trade and irrigation, and patronizing distinctive temple architecture and Telugu culture.
-
E.
Satavahana king
A Satavahana king is a ruler from the ancient Indian Satavahana dynasty, known for governing the Deccan region, promoting trade and culture, and issuing distinctive coinage and inscriptions.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:47 a.m.