Triple
T20096313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinwil |
E496409
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bubikon |
—
|
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: Bubikon | Statement: [Hinwil, locatedNear, Bubikon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bubikon Context triple: [Hinwil, locatedNear, Bubikon]
-
A.
Bubikon
chosen
Bubikon is a municipality in the canton of Zurich in Switzerland, known for its rural character and the historic Bubikon Commandery of the Knights Hospitaller.
-
B.
Büren an der Aare
Büren an der Aare is a small Swiss municipality in the canton of Bern, situated along the Aare River and known for its historic town center and riverside setting.
-
C.
Koppigen
Koppigen is a municipality in the canton of Bern in Switzerland, situated in the Emmental region.
-
D.
Zugerberg
Zugerberg is a scenic mountain and recreational area in the Swiss canton of Zug, known for its panoramic views over Lake Zug and the surrounding Alps.
-
E.
Bollingen
Bollingen is a small Swiss locality on the shores of Lake Zurich, known for its rural character and scenic lakeside setting.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666cc02481908780a415b19c05a2 |
completed | April 20, 2026, 5:46 p.m. |
Created at: April 11, 2026, 11:25 p.m.