Triple

T19340329
Position Surface form Disambiguated ID Type / Status
Subject Saanen E483737 entity
Predicate contains P35 FINISHED
Object Schönried 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: Schönried | Statement: [Saanen, contains, Schönried]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schönried
Context triple: [Saanen, contains, Schönried]
  • A. Schönried chosen
    Schönried is a Swiss alpine village and ski resort in the Bernese Oberland, known for its scenic mountain setting and proximity to the upscale resort area of Gstaad.
  • B. Meisenthal
    Meisenthal is a village in northeastern France renowned for its historic glassmaking tradition and cultural heritage.
  • C. Köstendorf
    Köstendorf is a small Austrian municipality in the state of Salzburg, known for its rural character and proximity to the city of Salzburg.
  • D. Luxenberg
    Luxenberg is an alternative spelling or variant form of the name "Luxemburg," which can refer to the European country Luxembourg or the surname of notable individuals such as revolutionary Rosa Luxemburg.
  • E. Offenberg
    Offenberg is a municipality in the Bavarian region of Germany, situated within the Regen district.
  • 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61856c0948190a3166b3bf3810e43 completed April 20, 2026, 12:13 p.m.
Created at: April 10, 2026, 1:33 p.m.