Triple
T34504236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jivitputrika Vrat |
E885839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu fasting ritual |
C45267
|
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 fasting ritual Context triple: [Jivitputrika Vrat, instanceOf, Hindu fasting ritual]
-
A.
Hindu rite of passage
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.
-
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 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.
-
D.
Jain religious ceremony
A Jain religious ceremony is a ritual practice involving prayers, offerings, vows, and meditative activities performed to honor the Tirthankaras, purify the soul, and advance on the path of non-violence and spiritual liberation.
-
E.
Hindu religious event
chosen
A Hindu religious event is a ritualistic or celebratory gathering rooted in Hindu beliefs and traditions, typically involving worship, offerings, prayers, and cultural practices to honor deities, mark sacred times, or observe life-cycle ceremonies.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.