Triple
T10450053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lhotse |
E246395
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Lobuche |
E881608
|
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: Lobuche | Statement: [Lhotse, nearbySettlement, Lobuche]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lobuche Context triple: [Lhotse, nearbySettlement, Lobuche]
-
A.
Lobuche
chosen
Lobuche is a small Sherpa village in Nepal’s Khumbu region that serves as a high-altitude stopover for trekkers and climbers heading toward Everest and nearby peaks.
-
B.
Tilicho Peak
Tilicho Peak is a high mountain in the Annapurna range of the Himalayas in Nepal, known for its dramatic slopes above Tilicho Lake and challenging climbing routes.
-
C.
Shkhara
Shkhara is a prominent peak in the Greater Caucasus mountain range, known as one of the highest and most challenging mountains in the region.
-
D.
Larkya Peak
Larkya Peak is a high Himalayan mountain in Nepal, known as one of the prominent summits of the Mansiri Himal range near the Manaslu region.
-
E.
Khumbu
Khumbu is a high-altitude region in northeastern Nepal famed for encompassing the Everest area and serving as the homeland of the Sherpa people.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe09af04819083db42f4de4cb0a9 |
completed | April 7, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4cbacad608190adddd91f13e4113b |
completed | April 19, 2026, 12:33 p.m. |
Created at: April 6, 2026, 12:17 p.m.