Triple
T22173168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Mellon area |
E547972
|
entity |
| Predicate | distanceToVancouverByFerryAndRoad |
P61372
|
FINISHED |
| Object | approximately 40 to 60 kilometers |
—
|
LITERAL FINISHED |
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: approximately 40 to 60 kilometers | Statement: [Port Mellon area, distanceToVancouverByFerryAndRoad, approximately 40 to 60 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToVancouverByFerryAndRoad Context triple: [Port Mellon area, distanceToVancouverByFerryAndRoad, approximately 40 to 60 kilometers]
-
A.
distanceToVancouverByRoad
chosen
Indicates the length of the route required to travel by road from a given place to Vancouver.
-
B.
distanceToVancouver
Indicates the spatial distance between a given entity’s location and the city of Vancouver.
-
C.
distanceFromVictoria
Indicates the measured distance between a given entity or location and Victoria.
-
D.
distanceToWhistlerByRoad
Indicates the road travel distance between a given place and Whistler.
-
E.
distanceToTofino_km
Indicates the distance, measured in kilometers, between a given location and Tofino.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a69c12c8190a03177b5b740456a |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.