Triple

T17820132
Position Surface form Disambiguated ID Type / Status
Subject Wiesbachhorn E444959 entity
Predicate hasSubpeak P7612 FINISHED
Object Mittleres Wiesbachhorn 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: Mittleres Wiesbachhorn | Statement: [Wiesbachhorn, hasSubpeak, Mittleres Wiesbachhorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mittleres Wiesbachhorn
Context triple: [Wiesbachhorn, hasSubpeak, Mittleres Wiesbachhorn]
  • A. Wiesbachhorn chosen
    Wiesbachhorn is a prominent alpine peak in the Austrian Alps, known for its impressive height and glaciated slopes within the Hohe Tauern range.
  • B. Fletschhorn
    Fletschhorn is a prominent mountain peak in the Swiss Pennine Alps, known for its glaciated slopes and popularity among alpine climbers.
  • C. Ottohorn
    Ottohorn is a mountain peak located within the Picket Range of the North Cascades in Washington State, known for its rugged terrain and challenging climbing routes.
  • D. Gspaltenhorn
    Gspaltenhorn is a prominent peak in the Bernese Alps of Switzerland, known for its rugged profile and alpine climbing routes.
  • E. Rimpfischhorn
    Rimpfischhorn is a prominent high-altitude mountain in the Swiss Pennine Alps, known for its glaciated slopes and challenging climbing 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e489101aa48190a1439d8cb683bba9 completed April 19, 2026, 7:49 a.m.
Created at: April 10, 2026, 10:15 a.m.