Triple
T37006858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruislip Gardens station |
E915824
|
entity |
| Predicate | hasAdjacentDepotAccess |
P88401
|
FINISHED |
| Object | West Ruislip depot |
E283007
|
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: West Ruislip depot | Statement: [Ruislip Gardens station, hasAdjacentDepotAccess, West Ruislip depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentDepotAccess Context triple: [Ruislip Gardens station, hasAdjacentDepotAccess, West Ruislip depot]
-
A.
hasAdjacentDepot
chosen
Indicates that one entity has a depot located directly next to or adjoining it.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
isPublicTransportDepot
Indicates that a location functions as a depot or base facility for public transportation vehicles and operations.
-
D.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
E.
isGroundTransportHubFor
Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e576cbc948190994ec2e9037ff01c |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.