Triple

T17470731
Position Surface form Disambiguated ID Type / Status
Subject Wädenswil E425405 entity
Predicate locatedInRegion P40 FINISHED
Object Zimmerberg 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: Zimmerberg | Statement: [Wädenswil, locatedInRegion, Zimmerberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zimmerberg
Context triple: [Wädenswil, locatedInRegion, Zimmerberg]
  • A. Zimmerberg chosen
    Zimmerberg is a hilly region in the canton of Zurich, Switzerland, overlooking Lake Zurich and encompassing several suburban municipalities.
  • B. Holterberg
    Holterberg is a prominent hilly nature area in the Netherlands known for its heathlands, forests, and hiking and cycling trails within the Sallandse Heuvelrug National Park.
  • C. Reisenberg
    Reisenberg is a small municipality in Lower Austria’s Baden District, known for its rural character and proximity to Vienna.
  • D. Belpberg
    Belpberg is a small former municipality in the canton of Bern, Switzerland, situated on a plateau above the Gürbetal valley and known for its rural, scenic landscape.
  • E. Enzberg
    Enzberg is a district of the town of Mühlacker in the state of Baden-Württemberg, 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451abab908190b6d9d8a64f7c2ea3 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.