Triple
T21177970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripura (three worlds) |
E521865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shakta theological concept |
C17403
|
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: Shakta theological concept Context triple: [Tripura (three worlds), instanceOf, Shakta theological concept]
-
A.
Supreme goddess in Shakta tradition
The supreme goddess in the Shakta tradition is the ultimate, all-encompassing divine reality and cosmic power (Shakti) from whom all gods, goddesses, and the universe itself arise and in whom they dissolve.
-
B.
concept in Hinduism
chosen
A concept in Hinduism is an abstract idea, principle, or belief—such as dharma, karma, or moksha—that helps explain the nature of reality, ethical conduct, and the spiritual path within the Hindu tradition.
-
C.
concept in Theosophy
A concept in Theosophy is an abstract idea or principle that explains aspects of spiritual evolution, cosmic structure, or hidden laws of nature within the theosophical worldview.
-
D.
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.
-
E.
Tantric tradition
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.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3 p.m.