Triple

T17591159
Position Surface form Disambiguated ID Type / Status
Subject Lucerne region E428450 entity
Predicate contains P35 FINISHED
Object Stanserhorn 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: Stanserhorn | Statement: [Lucerne region, contains, Stanserhorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stanserhorn
Context triple: [Lucerne region, contains, Stanserhorn]
  • A. Stanserhorn chosen
    Stanserhorn is a prominent mountain in central Switzerland’s Nidwalden canton, known for its panoramic views over Lake Lucerne and the surrounding Alps and for its open-top cable car.
  • B. 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.
  • C. Riederhorn
    Riederhorn is a mountain in the Swiss Alps overlooking the Aletsch Glacier in the canton of Valais.
  • D. Lauteraarhorn
    Lauteraarhorn is a prominent, steep pyramidal peak in the Swiss Bernese Alps, known for its challenging climbs and striking glaciated surroundings.
  • E. Strahlhorn
    Strahlhorn is a prominent 4,190-meter alpine peak in the Pennine Alps of Switzerland, popular with mountaineers for its glaciated routes and panoramic views.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469e6e3888190b73a5b6d7e8c0a55 completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 5:51 a.m.