Triple
T19482000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort St. John |
E487408
|
entity |
| Predicate | distanceToAlbertaBorder |
P136095
|
FINISHED |
| Object | approximately 75 km west of Alberta border |
—
|
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 75 km west of Alberta border | Statement: [Fort St. John, distanceToAlbertaBorder, approximately 75 km west of Alberta border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAlbertaBorder Context triple: [Fort St. John, distanceToAlbertaBorder, approximately 75 km west of Alberta border]
-
A.
distanceToCanadianBorder
Indicates the measured or estimated spatial distance between a given location and the nearest point on the Canadian national border.
-
B.
roadDistanceToBCBorder
Indicates the road travel distance from a given location to the border of British Columbia.
-
C.
distanceFromCalgary
Indicates the spatial distance between a given location and the city of Calgary.
-
D.
distanceToEdmonton
Indicates the spatial distance between a given entity’s location and the city of Edmonton.
-
E.
distanceToRegina
Indicates the spatial distance between a given entity and Regina.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343ab16481909b508ba0a08ea191 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.