Triple
T34888509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasHighwayRoute |
P11026
|
FINISHED |
| Object | Autoroute 20 |
—
|
NE NERFINISHED |
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: Autoroute 20 | Statement: [Montreal–Quebec City, hasHighwayRoute, Autoroute 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighwayRoute Context triple: [Montreal–Quebec City, hasHighwayRoute, Autoroute 20]
-
A.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
B.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
D.
hasTransportRoute
chosen
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
rangeHighwayApprox
Indicates that one entity is approximately within the range or vicinity of a highway associated with another entity.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4 p.m.