Triple
T29941791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Trade Centre office complex |
E760516
|
entity |
| Predicate | isIconicLocationWithin |
P13974
|
FINISHED |
| Object | Canada Place |
—
|
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: Canada Place | Statement: [World Trade Centre office complex, isIconicLocationWithin, Canada Place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIconicLocationWithin Context triple: [World Trade Centre office complex, isIconicLocationWithin, Canada Place]
-
A.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
B.
isLocalLandmark
chosen
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
C.
hasIconicArea
Indicates that an entity possesses a distinct, widely recognized area or region that is emblematic or characteristic of it.
-
D.
isIconicAddressOf
Indicates that one entity is a widely recognized, emblematic, or culturally significant address associated with the other entity.
-
E.
isNamedLocation
Indicates that an entity is a specific, identifiable place referred to by a proper name.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780791108190bfec07f0d7119674 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:22 p.m.