Triple
T27142958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin–Westport railway line |
E681863
|
entity |
| Predicate | terminusCounty |
P23957
|
FINISHED |
| Object | County Mayo |
—
|
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: County Mayo | Statement: [Dublin–Westport railway line, terminusCounty, County Mayo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCounty Context triple: [Dublin–Westport railway line, terminusCounty, County Mayo]
-
A.
northernTerminusCounty
Indicates that a county serves as the northern endpoint or terminus of a specified route, line, or feature.
-
B.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
-
D.
terminusProvinceWest
Indicates that the western terminus of an entity (such as a route or line) is located within a specified province.
-
E.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:10 a.m.