Triple
T28954935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bay–Ottawa |
E731132
|
entity |
| Predicate | usesRoadInfrastructureOf |
P77660
|
FINISHED |
| Object | Ontario |
—
|
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: Ontario | Statement: [North Bay–Ottawa, usesRoadInfrastructureOf, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoadInfrastructureOf Context triple: [North Bay–Ottawa, usesRoadInfrastructureOf, Ontario]
-
A.
usedTransportationInfrastructure
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
B.
isTransportationInfrastructure
Indicates that something functions as a physical facility or system designed to support the movement of people or goods, such as roads, railways, ports, or airports.
-
C.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
D.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
E.
usesPublicRoads
chosen
Indicates that an entity travels on, operates vehicles on, or otherwise makes use of publicly accessible roadways.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 8:46 a.m.