Triple

T17515576
Position Surface form Disambiguated ID Type / Status
Subject Rigi massif E426558 entity
Predicate accessibleFrom P1985 FINISHED
Object Vitznau 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: Vitznau | Statement: [Rigi massif, accessibleFrom, Vitznau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vitznau
Context triple: [Rigi massif, accessibleFrom, Vitznau]
  • A. Vitznau chosen
    Vitznau is a picturesque Swiss lakeside village in the canton of Lucerne, known as a gateway to Mount Rigi and a popular destination for scenic tourism on Lake Lucerne.
  • B. Sursee
    Sursee is a historic Swiss town in the canton of Lucerne, known for its well-preserved medieval old town and scenic setting near Lake Sempach.
  • C. Bettlach
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • D. Disentis
    Disentis is a Swiss Alpine village in the canton of Graubünden known for its Benedictine monastery and access to extensive skiing and mountain sports.
  • E. Kiental
    Kiental is a picturesque alpine valley and village in the Bernese Oberland region of Switzerland, known for its dramatic mountain scenery and hiking opportunities.
  • 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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4526097388190ba1a949064962a24 completed April 19, 2026, 3:56 a.m.
Created at: April 10, 2026, 5:49 a.m.