Triple
T14927640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montpelier railway station |
E372172
|
entity |
| Predicate | hasRailwayRegion |
P15232
|
FINISHED |
| Object | Western route |
—
|
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: Western route | Statement: [Montpelier railway station, hasRailwayRegion, Western route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayRegion Context triple: [Montpelier railway station, hasRailwayRegion, Western route]
-
A.
railwayRegion
chosen
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
B.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
C.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
D.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:35 a.m.