Triple

T13339993
Position Surface form Disambiguated ID Type / Status
Subject Unterengstringen E317798 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Schlieren E82313 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: Schlieren | Statement: [Unterengstringen, hasNeighboringMunicipality, Schlieren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schlieren
Context triple: [Unterengstringen, hasNeighboringMunicipality, Schlieren]
  • A. Schlieren chosen
    Schlieren is a municipality in the canton of Zurich in northern Switzerland, known as a suburban town within the Zurich metropolitan area.
  • B. Pleiße
    Pleiße is a river in eastern Germany that flows through the city of Leipzig and is a tributary of the White Elster.
  • C. Weissenberg
    Weissenberg is a small town in eastern Saxony, Germany, known historically for its proximity to the Napoleonic-era Battle of Bautzen.
  • D. Reichenbach
    Reichenbach is a German surname most notably associated with Hans Reichenbach, a prominent 20th-century philosopher of science and logical empiricist.
  • E. Seebach
    Seebach is a quarter in the northern part of Zurich, Switzerland, known for its residential areas and proximity to major transport links.
  • 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_69f730641f588190886119506e6dde8f completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 9:31 p.m.