Triple
T18242451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Tour-de-Peilz railway station |
E436851
|
entity |
| Predicate | distanceFromLausanneOnLine |
P100548
|
FINISHED |
| Object | approximately 21 km |
—
|
LITERAL 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: approximately 21 km | Statement: [La Tour-de-Peilz railway station, distanceFromLausanneOnLine, approximately 21 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromLausanneOnLine Context triple: [La Tour-de-Peilz railway station, distanceFromLausanneOnLine, approximately 21 km]
-
A.
distanceToLausanne
chosen
Indicates the measured distance between a given entity’s location and the city of Lausanne.
-
B.
distanceToGeneva
Indicates the spatial distance between a given entity and the location of Geneva.
-
C.
distanceToZurich_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Zurich.
-
D.
distanceFromBesançonKilometres
Indicates the distance, measured in kilometers, between an entity and the city of Besançon.
-
E.
distanceToBasel_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Basel.
- F. None of above.
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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e387f481909d72574fb7d17923 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.