Triple

T34148782
Position Surface form Disambiguated ID Type / Status
Subject Narasinga E875937 entity
Predicate instanceOf P0 FINISHED
Object VemulavadaChalukyaRuler C28087 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: VemulavadaChalukyaRuler
Context triple: [Narasinga, instanceOf, VemulavadaChalukyaRuler]
  • A. Vemulavada Chalukya ruler chosen
    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. 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. 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.
  • D. Yadava king
    A Yadava king is a ruler belonging to the Yadava dynasty, historically associated with the Yadu lineage in ancient and medieval India, often linked to regions like Mathura and later the Deccan.
  • E. 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.
  • 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_69f349abaa508190a820f206620efddc completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:54 a.m.