Triple
T21116443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chester railway station |
E520310
|
entity |
| Predicate | railCodeType |
P129805
|
FINISHED |
| Object | National Rail station code |
—
|
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: National Rail station code | Statement: [Chester railway station, railCodeType, National Rail station code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railCodeType Context triple: [Chester railway station, railCodeType, National Rail station code]
-
A.
railwayCodeType
chosen
Indicates the specific classification or type category assigned to a railway code within a railway coding system.
-
B.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
C.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
railStandard
Indicates that something conforms to, uses, or is governed by a particular railway or rail transport standard.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72106a3b48190a0efa51a74ae21f0 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:55 p.m.