Triple
T28079507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkdale area |
E709637
|
entity |
| Predicate | hasNearbyBusTerminal |
P15095
|
FINISHED |
| Object | Yorkdale Bus Terminal |
—
|
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: Yorkdale Bus Terminal | Statement: [Yorkdale area, hasNearbyBusTerminal, Yorkdale Bus Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBusTerminal Context triple: [Yorkdale area, hasNearbyBusTerminal, Yorkdale Bus Terminal]
-
A.
hasNearbyTramStop
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
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.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
-
D.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
E.
hasAdjacentBusStation
chosen
Indicates that one location has a bus station situated directly next to or very near it.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 27, 2026, 8:51 p.m.