Triple
T3593584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sears Canada |
E76082
|
entity |
| Predicate | notableStore |
P50099
|
FINISHED |
| Object | Toronto Eaton Centre store |
—
|
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: Toronto Eaton Centre store | Statement: [Sears Canada, notableStore, Toronto Eaton Centre store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStore Context triple: [Sears Canada, notableStore, Toronto Eaton Centre store]
-
A.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
-
B.
notableLibrary
Indicates that the subject is a library recognized for its significance, prominence, or special importance.
-
C.
notableHub
Indicates that an entity serves as a significant central point or focal location for activities, connections, or influence within a particular context.
-
D.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
E.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
- F. None of above. chosen
Provenance (4 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15bbbcc81908d6cf95f8e70c6ca |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9261a948190b67f6c6ac0dae2e9 |
completed | March 8, 2026, 6 p.m. |
Created at: March 8, 2026, 3:22 p.m.