Triple
T23342062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoga Tantra |
E591760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tantric tradition |
C18044
|
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: tantric tradition Context triple: [Yoga Tantra, instanceOf, tantric tradition]
-
A.
Tantric tradition
chosen
The Tantric tradition is a diverse set of esoteric spiritual practices and philosophies, originating in South Asia, that use ritual, meditation, visualization, and sometimes transgressive methods to transform ordinary experience into a path to enlightenment and divine union.
-
B.
Shaivite tradition
The Shaivite tradition is a major Hindu devotional and philosophical stream centered on the worship of Shiva as the supreme reality, encompassing diverse rituals, yogic practices, temple cultures, and theological schools across South Asia.
-
C.
Shaivite ascetic tradition
The Shaivite ascetic tradition is a spiritual path within Hinduism centered on devotion to Shiva, emphasizing renunciation, rigorous yogic and meditative disciplines, and the pursuit of liberation through detachment from worldly life.
-
D.
esoteric practice
An esoteric practice is a specialized, often secret or obscure set of spiritual, mystical, or philosophical techniques intended for a limited group of initiates rather than the general public.
-
E.
Mahavidya
Mahavidya is a conceptual class representing each of the ten great wisdom goddesses in Hindu Tantric tradition, embodying distinct cosmic powers, philosophical insights, and transformative spiritual functions.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:18 p.m.