Triple
T21567251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden |
E532191
|
entity |
| Predicate | distanceToRevelstoke |
P144271
|
FINISHED |
| Object | approximately 150 km 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 150 km by road | Statement: [Golden, distanceToRevelstoke, approximately 150 km by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRevelstoke Context triple: [Golden, distanceToRevelstoke, approximately 150 km by road]
-
A.
distanceFromSquamish
Indicates the measured spatial distance between a given entity and the location of Squamish.
-
B.
distanceToWhistlerByRoad
Indicates the road travel distance between a given place and Whistler.
-
C.
distanceFromVictoria
Indicates the measured distance between a given entity or location and Victoria.
-
D.
distanceFromQuesnel
Indicates the spatial distance between a given entity or location and Quesnel.
-
E.
distanceFromFortWilliam
Indicates the measured distance between an entity and Fort William.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c9f264819085b4807923860793 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.