Triple
T16460234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wohlen bei Bern |
E399786
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Wohlen b. 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 b. Bern | Statement: [Wohlen bei Bern, shortName, Wohlen b. Bern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wohlen b. Bern Context triple: [Wohlen bei Bern, shortName, Wohlen b. 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.
Wädenswil
Wädenswil is a Swiss town in the canton of Zurich known for its lakeside location, wine-growing tradition, and research institutes.
-
D.
Walchwil
Walchwil is a picturesque Swiss municipality in the canton of Zug, known for its scenic location on the eastern shore of Lake Zug and views of the surrounding Alps.
-
E.
Oetwil an der Limmat
Oetwil an der Limmat is a municipality in the canton of Zurich in Switzerland, situated along the Limmat River in the Limmat Valley 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_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_6a005817fa088190a0eb85016fe5afc4 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:10 a.m.