Triple
T10682974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worksop railway station |
E251801
|
entity |
| Predicate | isRailwayStationFor |
P27112
|
FINISHED |
| Object | Worksop town centre |
—
|
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: Worksop town centre | Statement: [Worksop railway station, isRailwayStationFor, Worksop town centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailwayStationFor Context triple: [Worksop railway station, isRailwayStationFor, Worksop town centre]
-
A.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
B.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
railwayStationFor
chosen
Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, or service.
-
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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc43b9481908f35490db93db76c |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.