Triple
T28942516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalesha |
E730489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chalukya ruler |
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: Chalukya ruler Context triple: [Mangalesha, instanceOf, 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.
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.
-
C.
Pushyabhuti dynasty ruler
A Pushyabhuti dynasty ruler is a monarch from the early medieval North Indian royal house, centered in Thanesar and later Kannauj, known for consolidating regional power and patronizing religion and culture, most prominently under King Harsha.
-
D.
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.
-
E.
Gurjara-Pratihara ruler
A Gurjara-Pratihara ruler is a monarch from the early medieval North Indian Gurjara-Pratihara dynasty, known for resisting Arab invasions and patronizing art, architecture, and regional political consolidation between the 8th and 11th centuries.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:37 a.m.