Triple
T26925720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhavagupta |
E677772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Later Gupta ruler |
C48972
|
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: Later Gupta ruler Context triple: [Madhavagupta, instanceOf, Later Gupta ruler]
-
A.
Chaulukya king
A Chaulukya king is a sovereign ruler from the Chaulukya (Solanki) dynasty that governed parts of western India, particularly Gujarat and Rajasthan, between the 10th and 13th centuries CE.
-
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.
medieval Indian ruler
chosen
A medieval Indian ruler is a sovereign who governed a region of the Indian subcontinent between roughly the 8th and 16th centuries, exercising political, military, and cultural authority within a dynastic or imperial framework.
-
D.
Hindu ruler
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.
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.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:09 a.m.