Triple
T10450031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lhotse |
E246395
|
entity |
| Predicate | hasSubpeak |
P7612
|
FINISHED |
| Object | Lhotse Shar |
E33536
|
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: Lhotse Shar | Statement: [Lhotse, hasSubpeak, Lhotse Shar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lhotse Shar Context triple: [Lhotse, hasSubpeak, Lhotse Shar]
-
A.
Lhotse
chosen
Lhotse is the world’s fourth-highest mountain, located near Mount Everest in the Himalayas on the border between Nepal and the Tibet Autonomous Region of China.
-
B.
Himalchuli
Himalchuli is a prominent high-altitude mountain peak in the Nepalese Himalayas, known as one of the major summits of the Mansiri Himal range.
-
C.
Machhapuchhre
Machhapuchhre is a distinctive, sacred Himalayan peak in north-central Nepal, famed for its fishtail-shaped summit and prominence in the Annapurna mountain range.
-
D.
Shishapangma
Shishapangma is one of the world’s fourteen eight-thousanders, a major Himalayan peak located entirely within Tibet, China.
-
E.
Gyachung Kang
Gyachung Kang is a prominent Himalayan mountain peak, one of the world’s highest, located between Nepal and China in the Mahalangur Himal range.
- 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_69e482d55a04819090d95f7a4abb6e29 |
completed | April 19, 2026, 7:23 a.m. |
Created at: April 6, 2026, 12:17 p.m.