Triple

T16874309
Position Surface form Disambiguated ID Type / Status
Subject Blüemlisalphütte E421257 entity
Predicate near P350 FINISHED
Object Hohtürli Pass E400978 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: Hohtürli Pass | Statement: [Blüemlisalphütte, near, Hohtürli Pass]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hohtürli Pass
Context triple: [Blüemlisalphütte, near, Hohtürli Pass]
  • A. Hohtürli Pass chosen
    Hohtürli Pass is a high mountain pass in the Swiss Alps that offers hikers panoramic views of the surrounding peaks and glaciers.
  • B. Karakash Pass
    Karakash Pass is a high mountain pass in the Kunlun Mountains of western China, historically used as a route between Xinjiang and the Tibetan Plateau.
  • C. Wakhjir Pass
    Wakhjir Pass is a high mountain pass in the Hindu Kush that forms a remote and rugged border crossing between Afghanistan and China.
  • D. Hochtor Pass
    Hochtor Pass is a high mountain pass in the Austrian Alps, best known as a key point along the scenic Grossglockner High Alpine Road.
  • E. Lamkhaga Pass
    Lamkhaga Pass is a high-altitude Himalayan mountain pass that serves as a challenging trekking route connecting Uttarakhand’s Uttarkashi region with Kinnaur in Himachal Pradesh.
  • 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_69d889d470fc8190b4aec199636c0c56 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3b7f5290481909e0fd0af30935fcd completed April 18, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c2b2e67c81908e2313491d16353f completed May 10, 2026, 5:38 p.m.
Created at: April 10, 2026, 5:29 a.m.