Triple
T35659216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Devon Railway |
E1030380
|
entity |
| Predicate | hadMajorStation |
P1071
|
FINISHED |
| Object | Newton Abbot 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: Newton Abbot railway station | Statement: [South Devon Railway, hadMajorStation, Newton Abbot railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorStation Context triple: [South Devon Railway, hadMajorStation, Newton Abbot railway station]
-
A.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
B.
hadRailwayStation
Indicates that a place or area previously possessed a railway station, which may no longer be in existence or operation.
-
C.
hasMajorRailwayStation
chosen
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
D.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
E.
hasMajorHubIn
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.