Triple
T31817400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bricket Wood railway station |
E812172
|
entity |
| Predicate | hasPassengerShelterOnly |
P198217
|
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: [Bricket Wood railway station, hasPassengerShelterOnly, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerShelterOnly Context triple: [Bricket Wood railway station, hasPassengerShelterOnly, yes]
-
A.
hasPassengerShelterOnEachPlatform
Indicates that every platform at a given location is equipped with a passenger shelter.
-
B.
isSheltered
Indicates that one entity provides or serves as protective cover or refuge for another entity.
-
C.
isPassengerOnly
Indicates that the subject entity is restricted to passenger use only and does not accommodate cargo, freight, or mixed-use purposes.
-
D.
hasShelteredEntrances
Indicates that an entity provides one or more entrances that are covered or protected from weather or external exposure.
-
E.
hasPassengerOnlyService
Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69fed3569ca881909f4291baeb665d9d |
completed | May 9, 2026, 6:25 a.m. |
Created at: April 30, 2026, 11:45 p.m.