Triple
T26073886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochrane, Alberta |
E657626
|
entity |
| Predicate | distanceToCalgaryDowntown |
P58471
|
FINISHED |
| Object | approximately 35 kilometres northwest |
—
|
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 35 kilometres northwest | Statement: [Cochrane, Alberta, distanceToCalgaryDowntown, approximately 35 kilometres northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCalgaryDowntown Context triple: [Cochrane, Alberta, distanceToCalgaryDowntown, approximately 35 kilometres northwest]
-
A.
distanceFromCalgary
chosen
Indicates the spatial distance between a given location and the city of Calgary.
-
B.
distanceToEdmonton
Indicates the spatial distance between a given entity’s location and the city of Edmonton.
-
C.
distanceToGrandePrairie_km
Indicates the distance, measured in kilometers, between a given entity’s location and Grande Prairie.
-
D.
isInDirectionFromCalgary
Indicates that one location lies in a specified compass or geographic direction when measured outward starting from Calgary.
-
E.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 26, 2026, 7:32 p.m.