Triple

T21646089
Position Surface form Disambiguated ID Type / Status
Subject Domhütte E534219 entity
Predicate hasViewOf P854 FINISHED
Object Täschhorn NE NERFINISHED

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: Täschhorn | Statement: [Domhütte, hasViewOf, Täschhorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Täschhorn
Context triple: [Domhütte, hasViewOf, Täschhorn]
  • A. Täschhorn chosen
    Täschhorn is a prominent 4,491-meter alpine peak in the Swiss canton of Valais, known for its steep faces and challenging climbing routes near the Matterhorn.
  • B. Lauteraarhorn
    Lauteraarhorn is a prominent, steep pyramidal peak in the Swiss Bernese Alps, known for its challenging climbs and striking glaciated surroundings.
  • C. Finsteraarhorn
    Finsteraarhorn is a prominent, glaciated peak in the Swiss Alps known for its remote location and striking pyramidal shape.
  • D. Riederhorn
    Riederhorn is a mountain in the Swiss Alps overlooking the Aletsch Glacier in the canton of Valais.
  • E. Oeschinenhorn
    Oeschinenhorn is a prominent peak in the Bernese Alps of Switzerland, forming part of the Blüemlisalp massif and known for its rugged alpine terrain and mountaineering routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5394c570819081dbbe7e0f98f7d3 completed April 27, 2026, 12:16 p.m.
Created at: April 16, 2026, 6:35 p.m.