Triple
T34888519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasRailBranding |
P39149
|
FINISHED |
| Object | Corridor (Via Rail) |
—
|
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: Corridor (Via Rail) | Statement: [Montreal–Quebec City, hasRailBranding, Corridor (Via Rail)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailBranding Context triple: [Montreal–Quebec City, hasRailBranding, Corridor (Via Rail)]
-
A.
usesRollingStockBrand
Indicates that one entity employs or operates rolling stock manufactured under a specific brand.
-
B.
railwayOperatorBranding
chosen
Indicates that one entity is responsible for the railway-related branding, livery, or visual identity applied to another entity (such as a train service, station, or rolling stock).
-
C.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
D.
notableTrainBrand
Indicates that an entity is a well-known or significant brand associated with trains or railway services.
-
E.
hasRailSymbol
Indicates that an entity is associated with or represented by a specific rail-related symbol or icon.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4 p.m.