Triple
T5788406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urmston railway station |
E128328
|
entity |
| Predicate | distanceFromManchesterOxfordRoad |
P13107
|
FINISHED |
| Object | approximately 5 miles west |
—
|
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 5 miles west | Statement: [Urmston railway station, distanceFromManchesterOxfordRoad, approximately 5 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromManchesterOxfordRoad Context triple: [Urmston railway station, distanceFromManchesterOxfordRoad, approximately 5 miles west]
-
A.
distanceToOxford
Indicates the spatial distance between a given entity and the location of Oxford.
-
B.
distanceToManchester
chosen
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
C.
distanceFromMiltonKeynes
Indicates the measured spatial distance between a given entity’s location and the location of Milton Keynes.
-
D.
distanceToManchesterAirport
Indicates the spatial distance between a given location or entity and Manchester Airport.
-
E.
distanceToRochdale
Indicates the spatial distance between a given entity’s location and the location of Rochdale.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a53d0148190bdebc4f5609939ac |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.