Triple

T22770306
Position Surface form Disambiguated ID Type / Status
Subject Goms E563536 entity
Predicate contains P35 FINISHED
Object Münster-Geschinen 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: Münster-Geschinen | Statement: [Goms, contains, Münster-Geschinen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Münster-Geschinen
Context triple: [Goms, contains, Münster-Geschinen]
  • A. Münster-Geschinen chosen
    Münster-Geschinen is a small alpine village in the Swiss canton of Valais, known for its traditional wooden houses and location in the upper Rhone valley.
  • B. Münsterlingen
    Münsterlingen is a municipality in the canton of Thurgau in northeastern Switzerland, situated on the southern shore of Lake Constance.
  • C. Mündershausen
    Mündershausen is a small village and district of the town Rotenburg an der Fulda in the state of Hesse, Germany.
  • D. Rüdinghausen
    Rüdinghausen is a district of the city of Witten in North Rhine-Westphalia, Germany, characterized by its residential areas and local amenities.
  • E. Gummersbach
    Gummersbach is a town in North Rhine-Westphalia, Germany, known as a regional center in the Bergisches Land and a location for higher education and industry.
  • 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_69e24554497c819080b996e071de27c2 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17b5cea44819097290351da9c488d completed April 29, 2026, 3:30 a.m.
Created at: April 17, 2026, 3:27 p.m.