Triple
T28079511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkdale area |
E709637
|
entity |
| Predicate | shoppingCentreInstanceOf |
P44100
|
FINISHED |
| Object | super-regional shopping mall |
—
|
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: super-regional shopping mall | Statement: [Yorkdale area, shoppingCentreInstanceOf, super-regional shopping mall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoppingCentreInstanceOf Context triple: [Yorkdale area, shoppingCentreInstanceOf, super-regional shopping mall]
-
A.
shoppingCenterInstanceOf
chosen
Indicates that a specific shopping center is an instance of a particular type or class of shopping centers.
-
B.
locationOfShoppingCenter
Indicates that a specified place is the geographic location where a particular shopping center is situated.
-
C.
isIndoorMall
Indicates that a shopping mall is located indoors, typically enclosed within a single building or connected interior space.
-
D.
shoppingCenterCountry
Indicates the country in which a given shopping center is located.
-
E.
hasShoppingMall
Indicates that one entity possesses, contains, or includes a shopping mall within its area or domain.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 8:51 p.m.