Triple
T21330975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Jérôme, Quebec |
E525895
|
entity |
| Predicate | distanceFromMontrealByRoad |
P89770
|
FINISHED |
| Object | approximately 45 kilometres |
—
|
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 45 kilometres | Statement: [Saint-Jérôme, Quebec, distanceFromMontrealByRoad, approximately 45 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMontrealByRoad Context triple: [Saint-Jérôme, Quebec, distanceFromMontrealByRoad, approximately 45 kilometres]
-
A.
distanceToOttawaByRoad
Indicates the length of the travel route between a place and Ottawa when moving along the road network rather than in a straight line.
-
B.
distanceToGatineauByRoad_km
Indicates the length, in kilometers, of the road route needed to travel from an entity to Gatineau.
-
C.
distanceToMontreal
chosen
Indicates the spatial distance between a given entity’s location and the city of Montreal.
-
D.
distanceFromQuebecCity
Indicates the measured distance between a given place or object and Quebec City.
-
E.
distanceToVancouverByRoad
Indicates the length of the route required to travel by road from a given place to Vancouver.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab530a1c81909bb37c2a3407d9e6 |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:42 p.m.