Triple
T31812141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HafenCity Hamburg GmbH |
E812036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal development company |
C36486
|
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: municipal development company Context triple: [HafenCity Hamburg GmbH, instanceOf, municipal development company]
-
A.
Mayoral development corporation
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.
-
B.
urban development company
chosen
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.
-
C.
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.
-
D.
Community Development Council
A Community Development Council is a representative body that collaborates with local stakeholders to identify community needs, plan and coordinate development initiatives, and oversee the implementation of projects that enhance the well-being and sustainability of the community.
-
E.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:44 p.m.