Triple
T5248130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevaram |
E118513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bhakti literature |
C1830
|
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: Bhakti literature Context triple: [Tevaram, instanceOf, Bhakti literature]
-
A.
Sanskrit literature
Sanskrit literature is the body of classical and post-classical writings in the Sanskrit language, encompassing religious scriptures, epic poetry, drama, philosophy, science, and aesthetics that shaped much of South Asian intellectual and cultural history.
-
B.
Hindu devotional hymn
A Hindu devotional hymn is a sacred song or chant expressing love, reverence, and supplication to a deity, often performed in worship, rituals, or personal devotion.
-
C.
religious literature
chosen
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
-
D.
Gaudiya Vaishnava
A Gaudiya Vaishnava is a follower of the devotional Hindu tradition centered on Sri Chaitanya Mahaprabhu, emphasizing loving devotion (bhakti) to Radha-Krishna as the Supreme Reality.
-
E.
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.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.