Triple
T16182148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Märkisches Viertel |
E392708
|
entity |
| Predicate | hasRenovationPhase |
P25681
|
FINISHED |
| Object | urban renewal projects since 1990s |
—
|
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: urban renewal projects since 1990s | Statement: [Märkisches Viertel, hasRenovationPhase, urban renewal projects since 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRenovationPhase Context triple: [Märkisches Viertel, hasRenovationPhase, urban renewal projects since 1990s]
-
A.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
B.
hasRenovatedFacade
Indicates that an entity has a building whose exterior facade has been renovated or updated.
-
C.
requiresRenovation
Indicates that an entity is in a condition that necessitates repair, updating, or refurbishment before it is suitable for normal use or standards.
-
D.
renovationPeriod
chosen
Indicates the time span during which an object, structure, or entity undergoes renovation or refurbishment.
-
E.
hasRenovationCost
Indicates that an entity is associated with a specific monetary cost required for its renovation.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205d858c8190802d44e08e3cdcd6 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.