Triple
T36885626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street, Manchester |
E911600
|
entity |
| Predicate | hasNearbyBusInterchange |
P33739
|
FINISHED |
| Object | Shudehill Interchange |
E569399
|
NE 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: Shudehill Interchange | Statement: [High Street, Manchester, hasNearbyBusInterchange, Shudehill Interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBusInterchange Context triple: [High Street, Manchester, hasNearbyBusInterchange, Shudehill Interchange]
-
A.
nearbyBusStation
Indicates that a bus station is located close to a given reference point or entity.
-
B.
hasNearbyTramStop
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
C.
hasNearbyInterchange
chosen
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
-
D.
hasAdjacentBusStation
Indicates that one location has a bus station situated directly next to or very near it.
-
E.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
- F. None of above.
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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfaf2b5748190ac92e48aa7036157 |
completed | June 26, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: May 3, 2026, 4:13 p.m.