Triple
T31676801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dufferin Grove |
E808420
|
entity |
| Predicate | hasNearbyShopping |
P191961
|
FINISHED |
| Object | Dufferin Mall |
—
|
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: Dufferin Mall | Statement: [Dufferin Grove, hasNearbyShopping, Dufferin Mall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyShopping Context triple: [Dufferin Grove, hasNearbyShopping, Dufferin Mall]
-
A.
hasNearbyCommercialFacilities
chosen
Indicates that a place is located close to one or more commercial facilities, such as shops, restaurants, or other businesses.
-
B.
hasConvenienceStore
Indicates that one entity possesses, contains, or is associated with a convenience store.
-
C.
hasShoppingDistrict
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
locationOfShoppingCenter
Indicates that a specified place is the geographic location where a particular shopping center is situated.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: April 30, 2026, 11:03 p.m.