Triple
T27678364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Bay–Departure Bay route |
E697840
|
entity |
| Predicate | primaryMainlandCityAccess |
P125473
|
FINISHED |
| Object | Vancouver metropolitan area |
—
|
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: Vancouver metropolitan area | Statement: [Horseshoe Bay–Departure Bay route, primaryMainlandCityAccess, Vancouver metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMainlandCityAccess Context triple: [Horseshoe Bay–Departure Bay route, primaryMainlandCityAccess, Vancouver metropolitan area]
-
A.
accessFromCity
chosen
Indicates that there is a way to reach or enter a place starting from a specified city.
-
B.
cityAccess
Indicates that an entity has permission or the ability to enter, use, or reach a particular city.
-
C.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
D.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
E.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 27, 2026, 2:45 p.m.