Triple
T14844759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swanage Railway |
E349055
|
entity |
| Predicate | fullRouteReopenedAsHeritageLine |
P37967
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Swanage Railway, fullRouteReopenedAsHeritageLine, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullRouteReopenedAsHeritageLine Context triple: [Swanage Railway, fullRouteReopenedAsHeritageLine, 1980s]
-
A.
openedAsHeritageRailway
chosen
Indicates that a railway line or route was reopened specifically for heritage or tourist purposes rather than for regular commercial transport service.
-
B.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
-
C.
reopenedHistoricRoute
Indicates that a previously closed or inactive historic route has been opened again for use or access.
-
D.
reopenedAsHeritageStation
Indicates that a station, once closed or repurposed, has been reopened specifically as a heritage or historical railway station.
-
E.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded291103c8190a64cfe700bfee197 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.