Triple
T30719692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexis Creek, British Columbia |
E782115
|
entity |
| Predicate | distanceToWilliamsLake |
P203247
|
FINISHED |
| Object | approximately 112 kilometres west by road |
—
|
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 112 kilometres west by road | Statement: [Alexis Creek, British Columbia, distanceToWilliamsLake, approximately 112 kilometres west by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWilliamsLake Context triple: [Alexis Creek, British Columbia, distanceToWilliamsLake, approximately 112 kilometres west by road]
-
A.
distanceFromFortWilliam
Indicates the measured distance between an entity and Fort William.
-
B.
distanceFromPowellRiver
Indicates the measured spatial distance between a given location and Powell River.
-
C.
distanceToLethbridge
Indicates the measured or calculated distance from a given entity or location to Lethbridge.
-
D.
distanceFromTimmins
Indicates the measured distance between a given location or entity and the reference location Timmins.
-
E.
distanceFromSquamish
Indicates the measured spatial distance between a given entity and the location of Squamish.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_6a0141fc48b481909f0ae4a73b0e1592 |
completed | May 11, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:36 p.m.