Triple
T21268625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villeneuve railway station |
E524194
|
entity |
| Predicate | distanceFromReferencePoint |
P140307
|
FINISHED |
| Object | 26.7 km from Lausanne |
—
|
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: 26.7 km from Lausanne | Statement: [Villeneuve railway station, distanceFromReferencePoint, 26.7 km from Lausanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromReferencePoint Context triple: [Villeneuve railway station, distanceFromReferencePoint, 26.7 km from Lausanne]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
hasDistanceReference
chosen
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
C.
distanceFromCentre
Indicates the measured or specified distance of an entity from a defined central point.
-
D.
distanceReferenceGroup
Indicates a relationship where one entity serves as the reference group from which the distance to another entity is measured or evaluated.
-
E.
distancesFrom
Indicates the measured spatial separation between one entity and one or more other entities.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4 p.m.