Triple

T20810289
Position Surface form Disambiguated ID Type / Status
Subject Regensdorf E512278 entity
Predicate borderedBy P224 FINISHED
Object Oberengstringen 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: Oberengstringen | Statement: [Regensdorf, borderedBy, Oberengstringen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberengstringen
Context triple: [Regensdorf, borderedBy, Oberengstringen]
  • A. Oberengstringen chosen
    Oberengstringen is a municipality in the canton of Zurich in Switzerland, located in the Limmat Valley near the city of Zurich.
  • B. Oeschibach
    Oeschibach is a mountain stream in the Bernese Oberland region of Switzerland that drains the waters of Oeschinen Lake into the Kander Valley.
  • C. Bettlach
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • D. Seewiesen
    Seewiesen is a research locality in Bavaria, Germany, best known for its ornithological and behavioral science institutes associated with Konrad Lorenz and other pioneering ethologists.
  • E. Oschwand
    Oschwand is a small locality in Switzerland known for its association with the Swiss painter Cuno Amiet, who lived and worked there.
  • 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_69e0b4cd25088190b48ca9700cd24efc completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2d27a4881908b34679385d8b94b completed April 21, 2026, 12:20 a.m.
Created at: April 16, 2026, 12:40 p.m.