Triple

T13339917
Position Surface form Disambiguated ID Type / Status
Subject Urdorf E317796 entity
Predicate borderedBy P224 FINISHED
Object Oberengstringen E317797 NE FINISHED

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: [Urdorf, borderedBy, Oberengstringen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberengstringen
Context triple: [Urdorf, 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. Bettlach
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • C. 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.
  • D. Sachseln
    Sachseln is a municipality in the Swiss canton of Obwalden, known as the home and pilgrimage site associated with the Swiss patron saint Nicholas of Flüe.
  • E. Untereggen
    Untereggen is a small Swiss municipality in the canton of St. Gallen, known for its rural character and location in the country’s northeastern region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99d01bf8481908cd3a99e5557b972 completed April 11, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7267132488190a62930e98be70640 completed May 3, 2026, 10:41 a.m.
Created at: April 9, 2026, 9:31 p.m.