Triple

T18345558
Position Surface form Disambiguated ID Type / Status
Subject Mittelhorn E439526 entity
Predicate near P350 FINISHED
Object Rosenhorn 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: Rosenhorn | Statement: [Mittelhorn, near, Rosenhorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rosenhorn
Context triple: [Mittelhorn, near, Rosenhorn]
  • A. Rosenhorn chosen
    Rosenhorn is a notable subsidiary peak in the Bernese Alps of Switzerland, forming part of the Wetterhorn massif.
  • B. Rosenstein
    Rosenstein is a surname most notably associated with Justin Rosenstein, the American software programmer and co-founder of Asana.
  • C. Rosenbad
    Rosenbad is a prominent government building complex in central Stockholm that houses the offices of the Prime Minister and the Swedish Government.
  • D. Kraushaar
    Kraushaar is a surname most notably associated with Raoul Kraushaar, an American film and television composer active in the mid-20th century.
  • E. Frauenthal
    Frauenthal is a historic theater and cultural landmark in Muskegon, Michigan, known for hosting a wide range of performing arts events.
  • 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_69d8b9175fec8190af865699b4e64d8c completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e514f3bb888190bdeea4c4d114a43b completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 10:37 a.m.