Triple
T19969150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedarnath peak |
E480022
|
entity |
| Predicate | accessPoint |
P1985
|
FINISHED |
| Object | Gaurikund |
—
|
NE NERFINISHED |
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: Gaurikund | Statement: [Kedarnath peak, accessPoint, Gaurikund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gaurikund Context triple: [Kedarnath peak, accessPoint, Gaurikund]
-
A.
Gaurikund
chosen
Gaurikund is a small pilgrimage town in Uttarakhand, India, serving as the traditional base and starting point for the trek to the Himalayan shrine of Kedarnath.
-
B.
Kalpeshwar
Kalpeshwar is a remote Hindu temple in the Garhwal Himalaya of Uttarakhand, India, revered as one of the Panch Kedar shrines dedicated to Lord Shiva.
-
C.
Rudrapur
Rudrapur is a town in the Indian state of Uttar Pradesh, known as a local commercial and agricultural center in the region.
-
D.
Rudrapur
Rudrapur is a rapidly developing industrial and commercial city in the Udham Singh Nagar district of Uttarakhand, India.
-
E.
Tapt Kund
Tapt Kund is a revered natural hot water spring near the Badrinath temple in Uttarakhand, India, where pilgrims customarily bathe before offering prayers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc7c2fc81909b89c549a5f99e4c |
completed | April 20, 2026, 5 p.m. |
Created at: April 10, 2026, 1:54 p.m.