Triple
T23291776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransPennine Route Upgrade |
E590051
|
entity |
| Predicate | includesRoute |
P4374
|
FINISHED |
| Object | Leeds to York rail corridor |
—
|
NE NERFINISHED |
How this triple was built (3 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: Leeds to York rail corridor | Statement: [TransPennine Route Upgrade, includesRoute, Leeds to York rail corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leeds to York rail corridor Context triple: [TransPennine Route Upgrade, includesRoute, Leeds to York rail corridor]
-
A.
London–Leeds rail route
The London–Leeds rail route is a key intercity railway corridor in England linking the capital with the major northern city of Leeds via important intermediate stops.
-
B.
Manchester to Leeds line
The Manchester to Leeds line is a key trans-Pennine railway route in northern England connecting major cities across the Pennines.
-
C.
Leeds to Hull Line
The Leeds to Hull Line is a key railway route in northern England connecting the city of Leeds with the port city of Hull, serving numerous intermediate towns and commuter stations.
-
D.
Sheffield–Leeds line
The Sheffield–Leeds line is a key railway route in northern England that connects the cities of Sheffield and Leeds, serving major intermediate towns and supporting both commuter and regional services.
-
E.
Leeds to Doncaster line
The Leeds to Doncaster line is a key railway route in West and South Yorkshire, England, linking the major cities of Leeds and Doncaster and serving numerous intermediate commuter stations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Leeds to York rail corridor Target entity description: The Leeds to York rail corridor is a key passenger and freight railway line in northern England linking the major cities of Leeds and York and forming part of the core TransPennine network.
-
A.
London–Leeds rail route
The London–Leeds rail route is a key intercity railway corridor in England linking the capital with the major northern city of Leeds via important intermediate stops.
-
B.
Manchester to Leeds line
The Manchester to Leeds line is a key trans-Pennine railway route in northern England connecting major cities across the Pennines.
-
C.
Leeds to Hull Line
The Leeds to Hull Line is a key railway route in northern England connecting the city of Leeds with the port city of Hull, serving numerous intermediate towns and commuter stations.
-
D.
Sheffield–Leeds line
The Sheffield–Leeds line is a key railway route in northern England that connects the cities of Sheffield and Leeds, serving major intermediate towns and supporting both commuter and regional services.
-
E.
Leeds to Doncaster line
The Leeds to Doncaster line is a key railway route in West and South Yorkshire, England, linking the major cities of Leeds and Doncaster and serving numerous intermediate commuter stations.
- F. None of above. chosen
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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cc20c08190a6a678befe1061dd |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:02 p.m.