Triple
T34085369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avani Avittam |
E874163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu ritual observance |
C35291
|
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 ritual observance Context triple: [Avani Avittam, instanceOf, Hindu ritual observance]
-
A.
Hindu ritual performance
Hindu ritual performance is the structured enactment of sacred practices—such as offerings, chants, gestures, and processions—through which devotees communicate with the divine, uphold cosmic order (dharma), and mark key life-cycle and calendrical events.
-
B.
Hindu temple ritual
A Hindu temple ritual is a structured sequence of sacred actions, chants, and offerings performed in a temple to honor deities, seek blessings, and maintain spiritual harmony between devotees and the divine.
-
C.
Hindu rite of passage
chosen
A Hindu rite of passage is a ceremonial ritual marking significant transitions in an individual’s life—such as birth, initiation, marriage, and death—according to Hindu religious and cultural traditions.
-
D.
practice in Hinduism
Practice in Hinduism refers to the diverse set of rituals, disciplines, and daily behaviors—such as worship (puja), meditation, yoga, pilgrimage, and ethical living—through which Hindus express devotion, seek spiritual growth, and align themselves with dharma.
-
E.
Vaishnavite ritual
Vaishnavite ritual is a structured set of devotional practices—such as chanting, offerings, and temple worship—performed to honor and seek the grace of Vishnu and his avatars.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.