Triple
T20626365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern Railway (Ireland) |
E506827
|
entity |
| Predicate | mainLine |
P24771
|
FINISHED |
| Object | Portadown–Armagh–Keady line |
—
|
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: Portadown–Armagh–Keady line | Statement: [Great Northern Railway (Ireland), mainLine, Portadown–Armagh–Keady line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Portadown–Armagh–Keady line Context triple: [Great Northern Railway (Ireland), mainLine, Portadown–Armagh–Keady line]
-
A.
Belfast–Portadown line
The Belfast–Portadown line is a key railway route in Northern Ireland connecting Belfast with the town of Portadown and forming part of the region’s main intercity and commuter rail network.
-
B.
Dundalk–Enniskillen line
The Dundalk–Enniskillen line was a historic Irish railway route that connected the town of Dundalk on the east coast to Enniskillen in the west, forming part of a key cross-country corridor in the island’s rail network.
-
C.
Dublin–Navan–Kingscourt line
The Dublin–Navan–Kingscourt line is a former Irish railway route that connected Dublin with the towns of Navan and Kingscourt, historically serving as an important regional passenger and freight corridor.
-
D.
Belfast–Portadown railway line
The Belfast–Portadown railway line is a key rail corridor in Northern Ireland connecting Belfast with Portadown and serving major commuter towns such as Lisburn.
-
E.
Belfast–Derry railway line
The Belfast–Derry railway line is a key Northern Ireland Railways route connecting Belfast with the city of Derry/Londonderry through several intermediate towns.
- 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: Portadown–Armagh–Keady line Target entity description: The Portadown–Armagh–Keady line was a regional railway route in Northern Ireland that connected the towns of Portadown, Armagh, and Keady as part of the Great Northern Railway (Ireland) network.
-
A.
Belfast–Portadown line
The Belfast–Portadown line is a key railway route in Northern Ireland connecting Belfast with the town of Portadown and forming part of the region’s main intercity and commuter rail network.
-
B.
Dundalk–Enniskillen line
The Dundalk–Enniskillen line was a historic Irish railway route that connected the town of Dundalk on the east coast to Enniskillen in the west, forming part of a key cross-country corridor in the island’s rail network.
-
C.
Dublin–Navan–Kingscourt line
The Dublin–Navan–Kingscourt line is a former Irish railway route that connected Dublin with the towns of Navan and Kingscourt, historically serving as an important regional passenger and freight corridor.
-
D.
Belfast–Portadown railway line
The Belfast–Portadown railway line is a key rail corridor in Northern Ireland connecting Belfast with Portadown and serving major commuter towns such as Lisburn.
-
E.
Belfast–Derry railway line
The Belfast–Derry railway line is a key Northern Ireland Railways route connecting Belfast with the city of Derry/Londonderry through several intermediate towns.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe576c081909231dc0d7304b9a9 |
completed | April 20, 2026, 10:42 p.m. |
Created at: April 16, 2026, 11:42 a.m.