Triple
T15037312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway 401 |
E378508
|
entity |
| Predicate | busiestSectionLocation |
P91034
|
FINISHED |
| Object | through Toronto |
—
|
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: through Toronto | Statement: [Highway 401, busiestSectionLocation, through Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busiestSectionLocation Context triple: [Highway 401, busiestSectionLocation, through Toronto]
-
A.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
highestSectionsLocatedIn
Indicates that the highest parts or sections of an entity are situated within a specified location or area.
-
C.
oftenLocatedAt
chosen
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
D.
locationOfTypeSection
Indicates that a particular location is designated as the section or area associated with a specific type or category.
-
E.
locatedInSectionOfBuilding
Indicates that one entity is situated within a specific section or area of a building.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82cf3848190b0b2b6c9e65bc70b |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:59 a.m.