Triple

T17403666
Position Surface form Disambiguated ID Type / Status
Subject Kirchlindach E423157 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Schüpfen 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üpfen | Statement: [Kirchlindach, hasNeighboringMunicipality, Schüpfen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schüpfen
Context triple: [Kirchlindach, hasNeighboringMunicipality, Schüpfen]
  • A. Schüpfen chosen
    Schüpfen is a municipality in the canton of Bern in Switzerland, located in the Seeland administrative district.
  • B. Zwiggelte
    Zwiggelte is a small village in the Dutch province of Drenthe, known for its rural character and agricultural surroundings.
  • C. Fischeln
    Fischeln is a district of the German city of Krefeld in the state of North Rhine-Westphalia.
  • D. Schüss
    Schüss is the German name for the River Suze, a watercourse flowing through the Jura region of Switzerland.
  • E. Dettenschwang
    Dettenschwang is a village and district of the market town Dießen am Ammersee in the Bavarian region of 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b051cc48190872278ee0b52240d completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:45 a.m.