Triple
T19883502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakta canon |
E477836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu scripture corpus |
C18236
|
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: Hindu scripture corpus Context triple: [Shakta canon, instanceOf, Hindu scripture corpus]
-
A.
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.
-
B.
Shaivite scripture
chosen
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.
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.
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.
-
E.
Shaiva scripture commentary
A Shaiva scripture commentary is an interpretive text that explains, analyzes, and contextualizes sacred Shaiva scriptures, clarifying their philosophical, ritual, and devotional meanings for practitioners and scholars.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.