Triple

T16460043
Position Surface form Disambiguated ID Type / Status
Subject Köniz E399782 entity
Predicate borderedBy P224 FINISHED
Object Wohlen bei Bern E399786 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: Wohlen bei Bern | Statement: [Köniz, borderedBy, Wohlen bei Bern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wohlen bei Bern
Context triple: [Köniz, borderedBy, Wohlen bei Bern]
  • A. Wohlen bei Bern chosen
    Wohlen bei Bern is a municipality in the canton of Bern, Switzerland, situated just north of the city of Bern within its metropolitan region.
  • B. Wohlen
    Wohlen is a municipality and regional center in the Swiss canton of Aargau, known for its industrial history and role as a local economic hub.
  • C. Wollerau, Switzerland
    Wollerau, Switzerland is a wealthy municipality on the shores of Lake Zurich known as a low-tax residence for affluent individuals and companies.
  • D. Zollikon
    Zollikon is an affluent suburban municipality on the shores of Lake Zurich, known for its residential character and proximity to the city of Zurich in Switzerland.
  • E. Oberrieden
    Oberrieden is a municipality in the canton of Zurich, Switzerland, situated on the western shore of Lake Zurich.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32d80e66c8190b2b3199efe9cfaa1 completed April 18, 2026, 7:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f53aff081909a75de6672f15f0e completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:10 a.m.