Triple
T31613804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Station, Montreal |
E806700
|
entity |
| Predicate | ceasedRailPassengerService |
P27833
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Windsor Station, Montreal, ceasedRailPassengerService, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedRailPassengerService Context triple: [Windsor Station, Montreal, ceasedRailPassengerService, 1993]
-
A.
withdrawnFromMainlinePassengerService
Indicates that something (typically a vehicle or route) has been taken out of regular, scheduled passenger service on the main line.
-
B.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
C.
railServiceEnded
chosen
Indicates that a previously operating rail service has been discontinued or terminated.
-
D.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
E.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:38 p.m.