Triple
T25281816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saravana lake |
E633842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sacred place in Hinduism |
C42728
|
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: sacred place in Hinduism Context triple: [Saravana lake, instanceOf, sacred place in Hinduism]
-
A.
place in Hindu tradition
chosen
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.
-
B.
Hindu holy city
A Hindu holy city is a sacred urban center revered in Hinduism, often associated with important temples, pilgrimage sites, mythological events, and ritual practices that attract devotees seeking spiritual merit and blessings.
-
C.
concept in Hinduism
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.
-
D.
Hindu religious event
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.
-
E.
Hindu cosmological realm
A Hindu cosmological realm is a metaphysical plane of existence within the layered universe of Hindu thought, inhabited by specific beings and governed by particular spiritual, moral, and karmic laws.
- 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.