Triple
T15135981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumbini Master Plan |
E361553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pilgrimage site development plan |
C34412
|
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: pilgrimage site development plan Context triple: [Lumbini Master Plan, instanceOf, pilgrimage site development plan]
-
A.
pilgrimage infrastructure project
chosen
A pilgrimage infrastructure project is a coordinated initiative to design, build, or upgrade facilities, routes, and services that support and enhance the experience, safety, and accessibility of religious or spiritual journeys.
-
B.
pilgrimage network
A pilgrimage network is an interconnected system of sacred sites, routes, institutions, and supporting services that collectively structure and facilitate the movement and experiences of pilgrims.
-
C.
pilgrimage base
A pilgrimage base is a central location or facility that serves as the primary gathering, preparation, and support point for pilgrims before, during, or after their spiritual journey.
-
D.
religious site expansion initiative
A religious site expansion initiative is a coordinated effort to enlarge, enhance, or develop existing sacred facilities and surrounding infrastructure to better serve the spiritual, cultural, and community needs of its faith community.
-
E.
pilgrimage account
A pilgrimage account is a narrative record of a journey to a sacred place, typically blending personal spiritual reflection with descriptions of travel experiences, rituals, and encounters along the way.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.