Triple
T29337501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhatwari |
E743948
|
entity |
| Predicate | nearbyPilgrimageRoute |
P38487
|
FINISHED |
| Object | Gangotri Dham route |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Gangotri Dham route | Statement: [Bhatwari, nearbyPilgrimageRoute, Gangotri Dham route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPilgrimageRoute Context triple: [Bhatwari, nearbyPilgrimageRoute, Gangotri Dham route]
-
A.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
B.
pilgrimageRouteTo
chosen
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
C.
pilgrimageStartingPoint
Indicates the location from which a pilgrimage journey is initiated or begins.
-
D.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
E.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
- F. None of above.
Provenance (3 batches)
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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 1:31 p.m.