Triple
T34800646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Montreal |
E1003208
|
entity |
| Predicate | isMajorIntercityRouteIn |
P192581
|
FINISHED |
| Object | Canada |
—
|
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: Canada | Statement: [Toronto–Montreal, isMajorIntercityRouteIn, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorIntercityRouteIn Context triple: [Toronto–Montreal, isMajorIntercityRouteIn, Canada]
-
A.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
B.
isMajorPassengerRoute
Indicates that a transportation route serves as a primary corridor carrying a high volume of passenger traffic between locations.
-
C.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
D.
isMajorTransportAxisIn
chosen
Indicates that a route or corridor functions as a primary or heavily used transportation pathway within a specified area or region.
-
E.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 3:59 p.m.