Triple
T13709858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Wohlen |
E328740
|
entity |
| Predicate | locatedNear |
P294
|
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: [Lake Wohlen, locatedNear, Wohlen bei Bern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wohlen bei Bern Context triple: [Lake Wohlen, locatedNear, 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.
Walperswil
Walperswil is a small municipality in the canton of Bern in Switzerland.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43949e6c8190ae5e4fa119cde33a |
completed | April 13, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d52b3708190ae0945e65b271556 |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.