Triple
T27678395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Bay–Langdale route |
E697841
|
entity |
| Predicate | startPointMunicipality |
P22794
|
FINISHED |
| Object | West Vancouver |
—
|
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: West Vancouver | Statement: [Horseshoe Bay–Langdale route, startPointMunicipality, West Vancouver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointMunicipality Context triple: [Horseshoe Bay–Langdale route, startPointMunicipality, West Vancouver]
-
A.
mainMunicipality
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
-
B.
startPointIsCapitalOf
Indicates that the starting point in a relation or path is a city that serves as the capital of the relevant region, country, or administrative entity.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
startCity
chosen
Indicates the city where a journey, route, or transportation service begins.
-
E.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
- 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_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 2:45 p.m.