Triple
T26154182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vauxhall Cross transport interchange |
E659911
|
entity |
| Predicate | hasBusStationStructure |
P165337
|
FINISHED |
| Object | Vauxhall bus station canopy |
—
|
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: Vauxhall bus station canopy | Statement: [Vauxhall Cross transport interchange, hasBusStationStructure, Vauxhall bus station canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusStationStructure Context triple: [Vauxhall Cross transport interchange, hasBusStationStructure, Vauxhall bus station canopy]
-
A.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
B.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
C.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
D.
hasBusStandType
Indicates the specific category or type of bus stand associated with a given bus stand entity.
-
E.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 26, 2026, 8:26 p.m.