Triple
T16460252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wohlen bei Bern |
E399786
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Wohlen village |
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 village | Statement: [Wohlen bei Bern, hasPart, Wohlen village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wohlen village Context triple: [Wohlen bei Bern, hasPart, Wohlen village]
-
A.
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.
-
B.
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.
-
C.
Wüllen
Wüllen is a district of the town of Ahaus in North Rhine-Westphalia, Germany, known for its rural character within the Münsterland region.
-
D.
Wehl
Wehl is a village in the Dutch province of Gelderland that formerly existed as an independent municipality before being incorporated into the nearby city of Doetinchem.
-
E.
Eggersriet village
Eggersriet village is a small rural settlement in the municipality of Eggersriet in the canton of St. Gallen, 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_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.