Triple
T5439302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castledawson |
E122091
|
entity |
| Predicate | historicalRailwayStationClosed |
P28717
|
FINISHED |
| Object | 20th century |
—
|
LITERAL FINISHED |
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: 20th century | Statement: [Castledawson, historicalRailwayStationClosed, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRailwayStationClosed Context triple: [Castledawson, historicalRailwayStationClosed, 20th century]
-
A.
formerRailwayStation
chosen
Indicates that a location previously functioned as a railway station but is no longer in active railway service.
-
B.
railwayStationOpened
Indicates that a railway station began operation or was officially opened on a specified date or in a specified time period.
-
C.
hasHeritageRailwayStation
Indicates that an entity possesses or is associated with a railway station that is preserved or operated as a heritage or historical railway facility.
-
D.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
E.
railwayWorksClosed
Indicates that a railway workshop, depot, or related railway works facility has ceased operations or been officially closed.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.