Triple
T6488351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Docklands of Amsterdam |
E146570
|
entity |
| Predicate | periodOfRedevelopment |
P54016
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Eastern Docklands of Amsterdam, periodOfRedevelopment, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfRedevelopment Context triple: [Eastern Docklands of Amsterdam, periodOfRedevelopment, late 20th century]
-
A.
majorRedevelopmentPeriod
chosen
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
B.
redevelopmentStartDate
Indicates the date on which a redevelopment project or process officially begins.
-
C.
redevelopmentEnd
Indicates the point in time or event at which a redevelopment process or project is considered completed or ceases.
-
D.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
E.
partOfRedevelopmentOf
Indicates that something is a component or phase within a larger redevelopment project or process.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a97fff88190b6f993c14df62649 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.