Triple
T34800653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Montreal |
E1003208
|
entity |
| Predicate | supportsInterprovincialTravel |
P111450
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Toronto–Montreal, supportsInterprovincialTravel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterprovincialTravel Context triple: [Toronto–Montreal, supportsInterprovincialTravel, true]
-
A.
allowsTravelAcross
chosen
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
B.
facilitatesTravelWithin
Indicates that one entity enables or makes it easier for another entity to move or travel within a specific area or region.
-
C.
validForTravelTo
Indicates that something (such as a document, item, or condition) is acceptable or authorized for use when traveling to a specified destination.
-
D.
offersInternationalTravel
Indicates that an entity provides or makes available travel services or opportunities that involve crossing national borders.
-
E.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
- 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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.