Triple
T25134440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Longstone |
E629615
|
entity |
| Predicate | hasRailwayStationFormer |
P89322
|
FINISHED |
| Object | Great Longstone 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: Great Longstone railway station | Statement: [Great Longstone, hasRailwayStationFormer, Great Longstone railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayStationFormer Context triple: [Great Longstone, hasRailwayStationFormer, Great Longstone railway station]
-
A.
hadRailwayStation
chosen
Indicates that a place or area previously possessed a railway station, which may no longer be in existence or operation.
-
B.
formerRailwayStation
Indicates that a location previously functioned as a railway station but is no longer in active railway service.
-
C.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
D.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
E.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465fdb83c81909ee750f7afdc15da |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:28 a.m.