Triple
T20222496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuchâtel railway station |
E495291
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Pontarlier |
—
|
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: Pontarlier | Statement: [Neuchâtel railway station, connectedTo, Pontarlier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pontarlier Context triple: [Neuchâtel railway station, connectedTo, Pontarlier]
-
A.
Pontarlier
chosen
Pontarlier is a historic town in eastern France near the Swiss border, known for its role in the absinthe industry and its location in the Jura Mountains.
-
B.
Peseux
Peseux is a former municipality in the canton of Neuchâtel in western Switzerland, now part of the city of Neuchâtel.
-
C.
Potigny
Potigny is a commune in the Calvados department of the Normandy region in northwestern France.
-
D.
Pougny
Pougny is a small French commune, likely located near the Swiss border in the Auvergne-Rhône-Alpes region.
-
E.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
Created at: April 11, 2026, 11:39 p.m.