Triple

T20135189
Position Surface form Disambiguated ID Type / Status
Subject Uttigen E491006 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Seftigen 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: Seftigen | Statement: [Uttigen, hasNeighboringMunicipality, Seftigen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seftigen
Context triple: [Uttigen, hasNeighboringMunicipality, Seftigen]
  • A. Seftigen chosen
    Seftigen is a small municipality in the canton of Bern, Switzerland, situated in a rural area of the Gürbetal valley.
  • B. Schellerten
    Schellerten is a rural municipality in Lower Saxony, Germany, characterized by its agricultural landscape and small-village communities.
  • C. Tägerwilen
    Tägerwilen is a municipality in the canton of Thurgau in northeastern Switzerland, located near Lake Constance and the German border.
  • D. Poitzen
    Poitzen is a small village in Lower Saxony, Germany, that forms part of the municipality of Faßberg.
  • E. Todenfeld
    Todenfeld is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66766e46c81908721fd47066dc9f8 completed April 20, 2026, 5:50 p.m.
Created at: April 11, 2026, 11:32 p.m.