Triple
T29314028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunnyside CTrain station |
E743328
|
entity |
| Predicate | hasPassengerAccessFrom |
P32331
|
FINISHED |
| Object | 10 Street NW |
—
|
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: 10 Street NW | Statement: [Sunnyside CTrain station, hasPassengerAccessFrom, 10 Street NW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerAccessFrom Context triple: [Sunnyside CTrain station, hasPassengerAccessFrom, 10 Street NW]
-
A.
passengerAccess
chosen
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasPassengerCheckInAccess
Indicates that an entity is permitted to perform or access passenger check-in functions for a given transport service or location.
-
D.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
E.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 1:18 p.m.