Triple
T25282127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harikatha (Tamil tradition) |
E633849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu religious practice |
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 religious practice Context triple: [Harikatha (Tamil tradition), instanceOf, Hindu religious practice]
-
A.
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.
-
B.
Hindu denomination
A Hindu denomination is a distinct religious tradition within Hinduism characterized by shared beliefs, practices, scriptures, and devotional focus, often centered on a particular deity or philosophical school.
-
C.
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.
-
D.
place in Hindu tradition
A place in Hindu tradition is a physical or sacred location—such as a temple, pilgrimage site, river, mountain, or city—imbued with religious, mythological, or spiritual significance and associated rituals.
-
E.
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.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:19 p.m.