Triple
T28574381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–North Bay |
E723194
|
entity |
| Predicate | northernCityConnected |
P60933
|
FINISHED |
| Object | North Bay |
—
|
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: North Bay | Statement: [Toronto–North Bay, northernCityConnected, North Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernCityConnected Context triple: [Toronto–North Bay, northernCityConnected, North Bay]
-
A.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
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.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
-
D.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
E.
connectsCityTo
chosen
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
- 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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:11 a.m.