Triple
T33899766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew Square, Edinburgh |
E869013
|
entity |
| Predicate | hasBusStationNearby |
P15095
|
FINISHED |
| Object | Edinburgh Bus Station |
—
|
NE NERFINISHED |
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: Edinburgh Bus Station | Statement: [St Andrew Square, Edinburgh, hasBusStationNearby, Edinburgh Bus Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusStationNearby Context triple: [St Andrew Square, Edinburgh, hasBusStationNearby, Edinburgh Bus Station]
-
A.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
B.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
-
C.
hasAdjacentBusStation
chosen
Indicates that one location has a bus station situated directly next to or very near it.
-
D.
hasBusStationStructure
Indicates that one entity serves as the physical structure or facility that functions as a bus station for another entity.
-
E.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:48 a.m.