Triple
T27142947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Great Western Railway |
E681862
|
entity |
| Predicate | railHeadForRegion |
P110961
|
FINISHED |
| Object | Galway (county) |
—
|
NE NERFINISHED |
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: Galway (county) | Statement: [Midland Great Western Railway, railHeadForRegion, Galway (county)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railHeadForRegion Context triple: [Midland Great Western Railway, railHeadForRegion, Galway (county)]
-
A.
railHead
chosen
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
-
B.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
C.
railwayZoneHeadquartersFor
Indicates that a location serves as the administrative headquarters for a particular railway zone.
-
D.
railLineOrigin
Indicates that a rail line begins or originates from a specified location or point.
-
E.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c2ed0c819091dde69fc6084d4a |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:10 a.m.