Triple
T11518745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloor–Yonge intersection |
E273100
|
entity |
| Predicate | isMajorCommercialArea |
P82485
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bloor–Yonge intersection, isMajorCommercialArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCommercialArea Context triple: [Bloor–Yonge intersection, isMajorCommercialArea, true]
-
A.
hasMajorCommercialCentre
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
B.
isMajorRegionalCenter
chosen
Indicates that a location functions as a primary hub of economic, administrative, or cultural activity within a specific geographic region.
-
C.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
D.
connectsToCommercialArea
Indicates that one location has a direct link, route, or access path to a commercial area.
-
E.
hasBusinessDistrict
Indicates that a place or administrative area contains or includes a designated business district within its boundaries.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fcf927081908ef89eff7ad833b0 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.