Triple
T20809474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Northland Railway station (Cochrane) |
E512258
|
entity |
| Predicate | keyStopFor |
P3386
|
FINISHED |
| Object | Ontario Northland passenger trains |
—
|
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: Ontario Northland passenger trains | Statement: [Ontario Northland Railway station (Cochrane), keyStopFor, Ontario Northland passenger trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyStopFor Context triple: [Ontario Northland Railway station (Cochrane), keyStopFor, Ontario Northland passenger trains]
-
A.
isKeyStopOn
chosen
Indicates that a particular stop functions as a primary or significant stop along a specified route or service.
-
B.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
C.
keyStep
Indicates a crucial or essential step within a larger process, sequence, or procedure.
-
D.
keyHolding
Indicates that one entity possesses and controls access to a key associated with another entity or resource.
-
E.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.