Triple
T37992555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto—Danforth |
E947854
|
entity |
| Predicate | borderNorthApproximate |
P63618
|
FINISHED |
| Object | Danforth Avenue and Taylor-Massey Creek area |
—
|
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: Danforth Avenue and Taylor-Massey Creek area | Statement: [Toronto—Danforth, borderNorthApproximate, Danforth Avenue and Taylor-Massey Creek area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderNorthApproximate Context triple: [Toronto—Danforth, borderNorthApproximate, Danforth Avenue and Taylor-Massey Creek area]
-
A.
boundaryTypeNorth
Indicates that one entity serves as or defines the northern boundary type or classification of another entity.
-
B.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
C.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
D.
borderedToNorthBy
chosen
Indicates that one entity lies directly to the north of another, sharing a common boundary along its southern edge.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:20 p.m.