Triple
T34800652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Montreal |
E1003208
|
entity |
| Predicate | supportsFreightFlows |
P101320
|
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, supportsFreightFlows, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFreightFlows Context triple: [Toronto–Montreal, supportsFreightFlows, true]
-
A.
freightConnections
chosen
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
B.
hasFreightFacility
Indicates that an entity is equipped with or connected to a facility used for handling, loading, unloading, or storing freight.
-
C.
supportsFlowOf
Indicates that one entity facilitates, enables, or maintains the movement or progression of another entity (such as a substance, resource, or process).
-
D.
supportsTraffic
Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
-
E.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
- 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.