Triple
T26036612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruppavai |
E647568
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vaishnavite scripture |
C21806
|
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: Vaishnavite scripture Context triple: [Tiruppavai, instanceOf, Vaishnavite scripture]
-
A.
Vaishnava scriptures
chosen
Vaishnava scriptures are sacred Hindu texts that focus on the worship, teachings, and stories of Vishnu and his avatars, guiding devotees in theology, devotion, and practice.
-
B.
Shaivite scripture
A Shaivite scripture is a sacred Hindu text that centers on the worship, mythology, philosophy, and rituals associated with the god Shiva and his manifestations.
-
C.
Gaudiya Vaishnava scripture commentary
A Gaudiya Vaishnava scripture commentary is an exegetical work that explains, interprets, and contextualizes sacred texts—such as the Bhagavad-gītā, Śrīmad-Bhāgavatam, and Chaitanya-caritāmṛta—according to the theological, devotional, and philosophical perspectives of the Gaudiya Vaishnava tradition.
-
D.
Varkari scripture
Varkari scripture refers to the devotional texts, abhangas, and hagiographies central to the Varkari tradition of Maharashtra, guiding personal devotion to Vithoba through teachings on bhakti, morality, and egalitarian spirituality.
-
E.
Hindu religious texts
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:08 a.m.