Triple
T17938197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to Godhead |
E448522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hare Krishna publication |
C40150
|
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: Hare Krishna publication Context triple: [Back to Godhead, instanceOf, Hare Krishna publication]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Soka Gakkai publication
A Soka Gakkai publication is any printed or digital work officially produced or endorsed by the Soka Gakkai organization to disseminate its Buddhist teachings, activities, and perspectives.
-
E.
Krishna-related sacred geography
Krishna-related sacred geography encompasses the network of places, landscapes, and pilgrimage sites associated with the life, legends, and worship of Krishna, understood as spiritually charged spaces that embody and reenact his divine presence and pastimes.
- F. None of above. chosen
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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.