Triple
T9119140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garuda Purana |
E218800
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vaishnava text |
C22098
|
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 text Context triple: [Garuda Purana, instanceOf, Vaishnava text]
-
A.
Vaishnava scriptures
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.
Hindu religious texts
chosen
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.
-
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.
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.
-
E.
Samkhya text
A Samkhya text is a philosophical work rooted in the ancient Indian Samkhya system that systematically analyzes reality through the dual principles of purusha (consciousness) and prakriti (primordial matter) to explain cosmology, psychology, and liberation.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:17 p.m.