Triple
T26739991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beecroft Road |
E674220
|
entity |
| Predicate | hasParallelCorridorRole |
P180305
|
FINISHED |
| Object | relief route to Yonge Street traffic |
—
|
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: relief route to Yonge Street traffic | Statement: [Beecroft Road, hasParallelCorridorRole, relief route to Yonge Street traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelCorridorRole Context triple: [Beecroft Road, hasParallelCorridorRole, relief route to Yonge Street traffic]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
parallelCorridorFor
Indicates that one corridor runs alongside and in the same general direction as another corridor, forming a parallel passage.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
E.
haveCrossBorderCorridor
Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 27, 2026, 3:48 a.m.