Triple
T18236045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courtice |
E436677
|
entity |
| Predicate | plannedRailService |
P130355
|
FINISHED |
| Object | GO Transit Lakeshore East extension |
—
|
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: GO Transit Lakeshore East extension | Statement: [Courtice, plannedRailService, GO Transit Lakeshore East extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedRailService Context triple: [Courtice, plannedRailService, GO Transit Lakeshore East extension]
-
A.
railAuthority
Indicates that an entity has official regulatory or operational control over railway systems or services.
-
B.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
C.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
D.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
E.
hasNationalRailService
Indicates that a place or facility is served by a country's national rail transportation network.
- F. None of above. chosen
Provenance (4 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b69a688190b140961eb298c36e |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:33 a.m.