Triple
T14131921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsier |
E350188
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Choulex |
E168322
|
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: Choulex | Statement: [Corsier, hasBorderWith, Choulex]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Choulex Context triple: [Corsier, hasBorderWith, Choulex]
-
A.
Choulex
chosen
Choulex is a small municipality in the canton of Geneva in southwestern Switzerland, known for its rural character and proximity to the city of Geneva.
-
B.
Choully
Choully is a small wine-producing village in the commune of Satigny in the canton of Geneva, Switzerland.
-
C.
Larche
Larche is a commune in the Corrèze department of south-central France, situated within the Brive-la-Gaillarde area.
-
D.
Larche
Larche is a small village in the French Alps near the Italian border, known as a gateway to the surrounding mountain passes and hiking routes.
-
E.
Livarchamps
Livarchamps is a small village in the municipality of Vaux-sur-Sûre in the Walloon region of Belgium.
- 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_69fcdf10e3948190b21968bc39094a8e |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 11:16 p.m.