Triple

T25399366
Position Surface form Disambiguated ID Type / Status
Subject Stanserhorn E636377 entity
Predicate hasSummitRestaurant P155363 FINISHED
Object yes LITERAL 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: yes | Statement: [Stanserhorn, hasSummitRestaurant, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSummitRestaurant
Context triple: [Stanserhorn, hasSummitRestaurant, yes]
  • A. hasMountainRestaurants chosen
    Indicates that a location or area contains one or more restaurants situated in a mountainous setting.
  • B. hasSummitVillage
    Indicates that an entity has an associated village located at or near its summit.
  • C. hasSummitRoad
    Indicates that there exists a road providing access to the summit or highest point of a geographic feature or structure.
  • D. hasSummitIn
    Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
  • E. hasSummitTrail
    Indicates that there exists a trail or route leading to the summit or highest point of a geographic feature.
  • F. None of above.

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_69e75db263888190b77fff9e2827b9a2 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f66c5c13808190887180099745673b completed May 2, 2026, 9:27 p.m.
PD Predicate disambiguation batch_69f66abddc448190a488852f8abdeb2c completed May 2, 2026, 9:21 p.m.
Created at: April 21, 2026, 1:50 p.m.