Triple
T12993145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohalpur |
E321965
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Nepalgunj |
E321961
|
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: Nepalgunj | Statement: [Kohalpur, hasRoadConnectionTo, Nepalgunj]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nepalgunj Context triple: [Kohalpur, hasRoadConnectionTo, Nepalgunj]
-
A.
Nepalgunj
chosen
Nepalgunj is a major city in southwestern Nepal known as a commercial and transportation hub near the Indian border.
-
B.
Janakpur
Janakpur is a historic cultural and religious center in the Mithila region, renowned as a major pilgrimage site associated with the Hindu epic Ramayana.
-
C.
Pokhara
Pokhara is a major lakeside city in central Nepal, known as a gateway to the Annapurna mountain range and a hub for trekking and adventure tourism.
-
D.
Tikapur
Tikapur is a town in far‑western Nepal known for its planned urban layout and the large riverside Tikapur Park along the Karnali River.
-
E.
Biratnagar
Biratnagar is a major industrial and commercial city in southeastern Nepal, serving as a key economic hub near the Indian border.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7765788190a9503ef055bc30ca |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbc4111c8190ace7bf505cd652ee |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:44 p.m.