Triple
T36696414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhageerath |
E906102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kadamba dynasty ruler |
C62339
|
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: Kadamba dynasty ruler Context triple: [Bhageerath, instanceOf, Kadamba dynasty ruler]
-
A.
Kadamba ruler
chosen
A Kadamba ruler is a monarch from the ancient Kadamba dynasty of South India, known for establishing one of the earliest native Kannada-speaking kingdoms and contributing to regional political, cultural, and architectural development.
-
B.
Chalukya ruler
A Chalukya ruler is a monarch from the Chalukya dynasty that governed parts of the Indian subcontinent between the 6th and 12th centuries, overseeing administration, warfare, and patronage of art and architecture.
-
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.
Wadiyar dynasty ruler
A Wadiyar dynasty ruler is a monarch from the royal family that governed the Kingdom of Mysore, overseeing its political, cultural, and economic development across several centuries in southern India.
-
E.
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.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.