Triple
T32270056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 4 Sheppard |
E824390
|
entity |
| Predicate | connectsToBusTerminal |
P136848
|
FINISHED |
| Object | Don Mills station 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: Don Mills station bus terminal | Statement: [Line 4 Sheppard, connectsToBusTerminal, Don Mills station bus terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToBusTerminal Context triple: [Line 4 Sheppard, connectsToBusTerminal, Don Mills station bus terminal]
-
A.
connectsToBusAt
chosen
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
B.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
C.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
D.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
E.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:42 a.m.