Triple
T21163035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basava |
E521487
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lingayat saint |
C30895
|
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: Lingayat saint Context triple: [Basava, instanceOf, Lingayat saint]
-
A.
Rajput saint
A Rajput saint is a spiritually revered figure from the Rajput community who embodies martial valor alongside deep religious devotion, often serving as a cultural and moral exemplar in regional traditions.
-
B.
Chaitanya Mahaprabhu
Chaitanya Mahaprabhu is a 16th-century Bengali saint and founder of Gaudiya Vaishnavism, revered as an incarnation of Krishna who propagated ecstatic devotion (bhakti) through congregational chanting of the holy names.
-
C.
medieval Indian saint
chosen
A medieval Indian saint is a revered spiritual figure from roughly the 8th to 17th centuries in the Indian subcontinent, known for devotional practice, philosophical teachings, and social reform rooted in religious traditions such as Hinduism, Islam (Sufism), Sikhism, or Jainism.
-
D.
Nayanar
Nayanar is a conceptual class representing a Shaivite saint or devotee from South India, traditionally revered for their intense devotion to Lord Shiva and their influential role in the Bhakti movement.
-
E.
Vaishnava saint
A Vaishnava saint is a devout practitioner and teacher within the Vaishnavism tradition of Hinduism, revered for their deep devotion to Vishnu (and his avatars), exemplary spiritual conduct, and role in guiding others on the path of bhakti (devotional worship).
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:59 p.m.