Triple
T30892611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramakrishna-Sarada pilgrimage circuit with Kamarpukur |
E786941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | devotional travel route |
C16187
|
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: devotional travel route Context triple: [Ramakrishna-Sarada pilgrimage circuit with Kamarpukur, instanceOf, devotional travel route]
-
A.
Buddhist pilgrimage
A Buddhist pilgrimage is a journey undertaken by devotees to sacred sites associated with the Buddha’s life, teachings, and relics, seeking spiritual merit, reflection, and deepened faith.
-
B.
Catholic pilgrimage
A Catholic pilgrimage is a devotional journey undertaken by the faithful to a sacred site associated with Jesus, Mary, the saints, or significant Church events, seeking spiritual growth, penance, and grace.
-
C.
Christian pilgrimage route
A Christian pilgrimage route is a spiritually significant path or network of paths that believers travel, often on foot, to reach holy sites associated with Jesus, saints, or important events in Christian history as an act of devotion, penance, or prayer.
-
D.
spiritual tourism destination
A spiritual tourism destination is a place travelers visit primarily to seek spiritual growth, religious experiences, or inner peace through sacred sites, rituals, teachings, or contemplative environments.
-
E.
Hindu pilgrimage circuit
chosen
A Hindu pilgrimage circuit is a traditional route linking multiple sacred sites that devotees visit, often in a prescribed sequence, to gain religious merit, spiritual purification, and blessings.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:49 p.m.