Triple
T14131919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsier |
E350188
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Collonge-Bellerive |
E69502
|
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: Collonge-Bellerive | Statement: [Corsier, hasBorderWith, Collonge-Bellerive]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Collonge-Bellerive Context triple: [Corsier, hasBorderWith, Collonge-Bellerive]
-
A.
Collonge-Bellerive
chosen
Collonge-Bellerive is a lakeside municipality in western Switzerland known for its residential character and location on the southern shore of Lake Geneva.
-
B.
Corseaux
Corseaux is a small Swiss municipality on the shores of Lake Geneva in the canton of Vaud, known for its scenic setting and residential character.
-
C.
Chens-sur-Léman
Chens-sur-Léman is a French commune on the southern shore of Lake Geneva in the Haute-Savoie department of the Auvergne-Rhône-Alpes region.
-
D.
Bardonnex
Bardonnex is a small Swiss municipality located in the canton of Geneva, near the country’s border with France.
-
E.
Chassieu
Chassieu is a commune in the Metropolis of Lyon in eastern France, known for its residential areas and proximity to the Lyon urban center.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bb3da748190a29652e17dbeac33 |
completed | May 8, 2026, 3:42 a.m. |
Created at: April 9, 2026, 11:16 p.m.