Triple
T25588960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veera Ballala III |
E641466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hoysala ruler |
C40389
|
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: Hoysala ruler Context triple: [Veera Ballala III, instanceOf, Hoysala ruler]
-
A.
Hoysala king
chosen
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.
-
B.
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.
-
C.
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.
-
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.
Chola king
A Chola king is a sovereign ruler of the medieval South Indian Chola dynasty, responsible for governing the kingdom, leading military campaigns, patronizing art and religion, and overseeing administration and trade.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:18 p.m.