Triple
T33387152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcarragh |
E854945
|
entity |
| Predicate | formerRailwayStationName |
P109087
|
FINISHED |
| Object | Falcarragh railway station |
—
|
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: Falcarragh railway station | Statement: [Falcarragh, formerRailwayStationName, Falcarragh railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRailwayStationName Context triple: [Falcarragh, formerRailwayStationName, Falcarragh railway station]
-
A.
formerRailwayStation
Indicates that a location previously functioned as a railway station but is no longer in active railway service.
-
B.
railwayStationAlsoKnownAs
chosen
Indicates that a railway station is referred to by an alternative name or alias.
-
C.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
-
D.
hadRailwayStation
Indicates that a place or area previously possessed a railway station, which may no longer be in existence or operation.
-
E.
originalRailroadTerminalReplaced
Indicates that one railroad terminal has been superseded or taken the place of another as the primary terminal.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:35 a.m.