Triple
T28574410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Sudbury |
E723195
|
entity |
| Predicate | hasNorthernCityOnRoute |
P65699
|
FINISHED |
| Object | Sudbury |
—
|
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: Sudbury | Statement: [Toronto–Sudbury, hasNorthernCityOnRoute, Sudbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthernCityOnRoute Context triple: [Toronto–Sudbury, hasNorthernCityOnRoute, Sudbury]
-
A.
hasMajorCityOnRoute
chosen
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
B.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
-
C.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
D.
isSuburbanRouteOf
Indicates that a given route functions as a suburban segment or service line belonging to, or operating as part of, a larger primary route or network.
-
E.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: April 28, 2026, 4:11 a.m.