Triple
T17771883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindustan–Tibet Road |
E443658
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Narkanda |
E1105213
|
NE 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: Narkanda | Statement: [Hindustan–Tibet Road, passesNear, Narkanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Narkanda Context triple: [Hindustan–Tibet Road, passesNear, Narkanda]
-
A.
Narkanda
chosen
Narkanda is a scenic hill station in Himachal Pradesh, India, known for its apple orchards, skiing slopes, and panoramic Himalayan views.
-
B.
Tanakpur
Tanakpur is a small town in Uttarakhand, India, known as a gateway to the Kumaon region and a key transit point to the neighboring country of Nepal.
-
C.
Karanpur
Karanpur is a town located in the Ganganagar district of the northern Indian state of Rajasthan.
-
D.
Bilaspuri
Bilaspuri is an Indo-Aryan language spoken primarily in the Bilaspur region of Himachal Pradesh in northern India.
-
E.
Nakodar
Nakodar is a prominent town in the Indian state of Punjab, known for its historical significance and cultural heritage within the Jalandhar region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e486005770819085d637279b2334eb |
completed | April 19, 2026, 7:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a032ffab0c48190bb03673653fa6fb8 |
completed | May 12, 2026, 1:49 p.m. |
Created at: April 10, 2026, 10:11 a.m.