Triple
T28949565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Vancouver from the North Shore |
E730969
|
entity |
| Predicate | transportLinkVisible |
P193052
|
FINISHED |
| Object | SeaBus |
—
|
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: SeaBus | Statement: [City of Vancouver from the North Shore, transportLinkVisible, SeaBus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportLinkVisible Context triple: [City of Vancouver from the North Shore, transportLinkVisible, SeaBus]
-
A.
transportLinkType
Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
-
B.
servesTransportLinks
Indicates that one entity provides or supports transportation connections or routes for another entity or area.
-
C.
isTransportationLinkBetween
Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
-
D.
transportHubScope
Indicates the extent or range of areas, routes, or services that a particular transport hub covers or connects.
-
E.
transportationLinksTo
Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
- F. None of above. chosen
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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: April 28, 2026, 8:42 a.m.