Triple
T28325446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea to Sky Country |
E717392
|
entity |
| Predicate | isScenicRouteBetween |
P101306
|
FINISHED |
| Object | 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: Vancouver | Statement: [Sea to Sky Country, isScenicRouteBetween, Vancouver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicRouteBetween Context triple: [Sea to Sky Country, isScenicRouteBetween, Vancouver]
-
A.
isScenicConnectorBetween
chosen
Indicates that something serves as a visually appealing route or link connecting two locations or entities.
-
B.
hasScenicRoutes
Indicates that one location, path, or area offers routes that are visually attractive or notable for their natural or aesthetic scenery.
-
C.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
D.
hasScenicRouteType
Indicates that a route is associated with a specific type or category of scenic quality or scenic designation.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492da6f081908a86dba0ffef5610 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:27 a.m.