Triple
T5776631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijk Havengebied |
E127457
|
entity |
| Predicate | redevelopmentIntensified |
P52998
|
FINISHED |
| Object | 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: 1990s | Statement: [Oostelijk Havengebied, redevelopmentIntensified, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopmentIntensified Context triple: [Oostelijk Havengebied, redevelopmentIntensified, 1990s]
-
A.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
B.
redevelopmentTo
Indicates a transformation relationship where one entity is redeveloped, converted, or repurposed into another entity.
-
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.
redevelopmentFrom
Indicates that one entity is created or transformed as a result of redeveloping or repurposing another pre-existing entity.
-
E.
redevelopmentPeaked
chosen
Indicates that the intensity or extent of redevelopment activity has reached its highest point within a given period or context.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.