Triple
T30535406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterfront Toronto |
E777128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public development corporation |
C16893
|
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: public development corporation Context triple: [Waterfront Toronto, instanceOf, public development corporation]
-
A.
urban development company
An urban development company is an organization that plans, finances, and executes projects to design, build, and revitalize city spaces, infrastructure, and real estate in alignment with economic, social, and environmental goals.
-
B.
Mayoral development corporation
chosen
A mayoral development corporation is a public body established by a city’s mayor to lead and coordinate regeneration, planning, and economic development within a designated urban area.
-
C.
economic development agency
An economic development agency is an organization, typically public or public–private, that designs and implements programs to attract investment, support businesses, and promote sustainable economic growth within a specific region.
-
D.
sustainable urban development company
A sustainable urban development company plans, designs, and builds city spaces and infrastructure that minimize environmental impact, promote social equity, and support long-term economic resilience.
-
E.
property development joint venture
A property development joint venture is a collaborative business arrangement in which two or more parties pool capital, expertise, and resources to plan, finance, develop, and sometimes operate a real estate project while sharing risks, costs, and returns.
- F. None of above.
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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:18 p.m.