Triple
T34154621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Vancouver public transit network |
E876098
|
entity |
| Predicate | airportConnectionLine |
P23780
|
FINISHED |
| Object | Canada Line |
—
|
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: Canada Line | Statement: [Metro Vancouver public transit network, airportConnectionLine, Canada Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportConnectionLine Context triple: [Metro Vancouver public transit network, airportConnectionLine, Canada Line]
-
A.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
B.
connectsWithAirport
chosen
Indicates that there is a direct transportation or operational link established between an entity and an airport.
-
C.
airportLocationRelation
Indicates a spatial or administrative relationship specifying where an airport is located relative to a geographic area or jurisdiction.
-
D.
airportLineRole
Indicates the specific functional role or responsibility an entity has in relation to an airport transit line or route.
-
E.
servesPassengerTrafficTo
Indicates that a transportation facility or service provides regular passenger traffic access or operations to a particular location or area.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:54 a.m.