Triple
T25682380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steeles Avenue East |
E643973
|
entity |
| Predicate | partOfBoundaryOf |
P101494
|
FINISHED |
| Object | City of Toronto northern boundary |
—
|
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: City of Toronto northern boundary | Statement: [Steeles Avenue East, partOfBoundaryOf, City of Toronto northern boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBoundaryOf Context triple: [Steeles Avenue East, partOfBoundaryOf, City of Toronto northern boundary]
-
A.
isPartOfLargerBoundary
chosen
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 21, 2026, 8:02 p.m.