Triple
T8283112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MedienHafen |
E193726
|
entity |
| Predicate | urbanRedevelopmentType |
P5744
|
FINISHED |
| Object | waterfront regeneration |
—
|
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: waterfront regeneration | Statement: [MedienHafen, urbanRedevelopmentType, waterfront regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRedevelopmentType Context triple: [MedienHafen, urbanRedevelopmentType, waterfront regeneration]
-
A.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
-
B.
urbanDevelopmentType
chosen
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
C.
redevelopmentProject
Indicates a project involving the renewal, improvement, or transformation of an existing area, structure, or infrastructure, typically replacing or upgrading what was previously there.
-
D.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
E.
redevelopmentTo
Indicates a transformation relationship where one entity is redeveloped, converted, or repurposed into another entity.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7aceec8881909cdfa488dfedc0f5 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.