Triple
T24279191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijayalaya Chola |
E605491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chola 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: Chola ruler Context triple: [Vijayalaya Chola, instanceOf, Chola 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.
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.
-
C.
Satavahana king
A Satavahana king is a ruler from the ancient Indian Satavahana dynasty, known for governing the Deccan region, promoting trade and culture, and issuing distinctive coinage and inscriptions.
-
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.
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.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.