Triple
T2986105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayes railway station (Bromley) |
E80627
|
entity |
| Predicate | hasCycleParking |
P1709
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hayes railway station (Bromley), hasCycleParking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCycleParking Context triple: [Hayes railway station (Bromley), hasCycleParking, yes]
-
A.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
B.
hasParkingNearby
Indicates that a location has one or more parking facilities or spaces available within a close surrounding area.
-
C.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
D.
hasBicycleFacilities
chosen
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
E.
parkingRequirement
Indicates the specified conditions or obligations related to providing or using parking associated with an entity or activity.
- 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.