Triple
T32207845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishikesh railway station |
E822718
|
entity |
| Predicate | servesPilgrimageSeasonTraffic |
P45121
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rishikesh railway station, servesPilgrimageSeasonTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPilgrimageSeasonTraffic Context triple: [Rishikesh railway station, servesPilgrimageSeasonTraffic, yes]
-
A.
servesPilgrimageTrafficFrom
Indicates that a location or facility accommodates or handles pilgrimage-related traffic originating from a specified place.
-
B.
servesSeasonalTraffic
chosen
Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
-
C.
servesPilgrimTrafficTo
Indicates that a location or entity functions as a route, hub, or provider facilitating the movement or flow of pilgrim traffic to a specified destination.
-
D.
pilgrimageSeason
Indicates the time period or season during which religious pilgrimages customarily take place.
-
E.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 12:37 a.m.