Triple
T10222520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagavat Paricaya |
E242615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vaishnava literature |
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: Vaishnava literature Context triple: [Bhagavat Paricaya, instanceOf, Vaishnava literature]
-
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 poet-saints
Shaivite poet-saints are devotional lyricists and mystics who composed and sang hymns in praise of the Hindu god Shiva, shaping regional bhakti traditions and religious literature through their ecstatic, often socially radical poetry.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:10 a.m.