Triple

T8309749
Position Surface form Disambiguated ID Type / Status
Subject Khumbu E194560 entity
Predicate contains P35 FINISHED
Object Lhotse 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 | Statement: [Khumbu, contains, Lhotse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lhotse
Context triple: [Khumbu, contains, Lhotse]
  • 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. Cho Oyu
    Cho Oyu is the world’s sixth-highest mountain, an 8,188-meter peak in the Mahalangur Himal section of the Himalayas near the Nepal–China border.
  • 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. Manaslu
    Manaslu is the eighth-highest mountain in the world, a prominent 8,000-meter peak in the Nepalese Himalayas renowned for its challenging climbing routes and dramatic ridgelines.
  • E. Kangchenjunga
    Kangchenjunga is the world’s third-highest mountain, a massive peak in the eastern Himalayas on the border between Nepal and India.
  • 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_69ca82e613e88190bf8139669bbd0d53 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7f2d2c30819095075940479b75a7 completed March 31, 2026, 8 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0f32101e08190888a1f44c2224e1e completed April 4, 2026, 11:16 a.m.
Created at: March 30, 2026, 5:54 p.m.