Triple
T2986110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayes railway station (Bromley) |
E80627
|
entity |
| Predicate | directionFromLondonTerminus |
P15847
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Hayes railway station (Bromley), directionFromLondonTerminus, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonTerminus Context triple: [Hayes railway station (Bromley), directionFromLondonTerminus, south]
-
A.
directionFromLondon
chosen
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
C.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
-
D.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
E.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
- 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.