Triple
T9010758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ucluelet |
E215462
|
entity |
| Predicate | distanceToTofino_km |
P85710
|
FINISHED |
| Object | approximately 40 |
—
|
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 | Statement: [Ucluelet, distanceToTofino_km, approximately 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTofino_km Context triple: [Ucluelet, distanceToTofino_km, approximately 40]
-
A.
distanceFromNanaimo
Indicates the spatial distance between a given location and Nanaimo.
-
B.
distanceToVancouverByRoad
Indicates the length of the route required to travel by road from a given place to Vancouver.
-
C.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
-
D.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
E.
distanceFromTimmins
Indicates the measured distance between a given location or entity and the reference location Timmins.
- F. None of above. chosen
Provenance (4 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c1571881908d0b144786b5ee1f |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:06 p.m.