Triple
T2986175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern (train operating company) |
E80629
|
entity |
| Predicate | railCodeSystem |
P27071
|
FINISHED |
| Object | National Rail station codes |
—
|
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 codes | Statement: [Southeastern (train operating company), railCodeSystem, National Rail station codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railCodeSystem Context triple: [Southeastern (train operating company), railCodeSystem, National Rail station codes]
-
A.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
railcode
chosen
Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
-
D.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
E.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.