Triple
T25813879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elton and Orston railway station |
E650195
|
entity |
| Predicate | hasRegionalRailCode |
P129805
|
FINISHED |
| Object | EMT area |
—
|
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: EMT area | Statement: [Elton and Orston railway station, hasRegionalRailCode, EMT area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalRailCode Context triple: [Elton and Orston railway station, hasRegionalRailCode, EMT area]
-
A.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
B.
isRegionalFreightRailroad
Indicates that a railroad operates primarily as a freight carrier within a specific geographic region rather than on a national or long-distance network.
-
C.
railwayCodeType
chosen
Indicates the specific classification or type category assigned to a railway code within a railway coding system.
-
D.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
E.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 22, 2026, 7:12 a.m.