Triple
T22411686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1250 René-Lévesque |
E554007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | skyscraper in Montreal |
C46246
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: skyscraper in Montreal Context triple: [1250 René-Lévesque, instanceOf, skyscraper in Montreal]
-
A.
civic skyscraper
A civic skyscraper is a tall, prominently located high-rise building that houses public or governmental functions, symbolizing civic identity and serving as a hub for community services and administration.
-
B.
skyscraper in Seattle
A skyscraper in Seattle is a tall, multi-story commercial or mixed-use building that defines the city's skyline, often featuring modern architecture, glass facades, and views of Puget Sound and the surrounding mountains.
-
C.
skyscraper in Hong Kong
A skyscraper in Hong Kong is a tall, high-density commercial or residential building that contributes to the city’s iconic vertical skyline, often integrating mixed-use spaces and advanced structural engineering to maximize limited urban land.
-
D.
megatall skyscraper
A megatall skyscraper is an exceptionally high-rise building exceeding 600 meters in height, designed to maximize vertical space for mixed-use functions while showcasing advanced engineering and architectural innovation.
-
E.
skyscraper in Berlin
A skyscraper in Berlin is a tall, multi-story commercial or mixed-use building that rises prominently above the city’s predominantly mid-rise skyline, integrating modern architecture with the urban fabric and historical context of the German capital.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.