Triple

T20114167
Position Surface form Disambiguated ID Type / Status
Subject Oeschinen Lake E490409 entity
Predicate hasViewOf P854 FINISHED
Object Fründenhorn 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: Fründenhorn | Statement: [Oeschinen Lake, hasViewOf, Fründenhorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fründenhorn
Context triple: [Oeschinen Lake, hasViewOf, Fründenhorn]
  • A. Fründenhorn chosen
    Fründenhorn is a prominent mountain peak in the Bernese Alps of Switzerland, known for its glaciers and alpine climbing routes.
  • B. Gspaltenhorn
    Gspaltenhorn is a prominent peak in the Bernese Alps of Switzerland, known for its rugged profile and alpine climbing routes.
  • C. Zwölferhorn
    Zwölferhorn is a prominent mountain in Austria’s Salzkammergut region, known for its panoramic views over Wolfgangsee and the surrounding Alps.
  • D. Bettmerhorn
    Bettmerhorn is a mountain in the Swiss Alps known for its panoramic views over the Aletsch Glacier and its role as a popular destination for skiing and hiking.
  • E. Fiescherhorn
    Fiescherhorn is a prominent peak in the Bernese Alps of Switzerland, known for its glaciated slopes and challenging alpine climbs.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666e31af081908d8e0c867c388a73 completed April 20, 2026, 5:48 p.m.
Created at: April 11, 2026, 11:29 p.m.