Triple
T23695861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Highway 69 |
E585442
|
entity |
| Predicate | isPartOfCorridorTo |
P85888
|
FINISHED |
| Object | Trans-Canada Highway near 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: Trans-Canada Highway near Sudbury | Statement: [Ontario Highway 69, isPartOfCorridorTo, Trans-Canada Highway near Sudbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCorridorTo Context triple: [Ontario Highway 69, isPartOfCorridorTo, Trans-Canada Highway near Sudbury]
-
A.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
onCorridorBetween
Indicates that one entity is located along the corridor that lies between two other reference entities or areas.
-
D.
inCorridor
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
-
E.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c65ab88190be59a8fb731cf030 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.