Triple
T25879906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunaga Vijayaditya III |
E652018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Chalukya ruler |
C8916
|
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 ruler Context triple: [Gunaga Vijayaditya III, instanceOf, Eastern Chalukya ruler]
-
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.
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.
-
C.
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.
-
D.
Hindu ruler
chosen
A Hindu ruler is a sovereign or monarch who governs a territory while adhering to, promoting, or being culturally shaped by Hindu religious, social, and philosophical traditions.
-
E.
pre-Mataram ruler
A pre-Mataram ruler is a monarch or chieftain who governed territories in the Indonesian archipelago before the rise of the Mataram Kingdom, shaping early political and cultural developments in the region.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:16 a.m.