Triple
T938215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary Wharf |
E20245
|
entity |
| Predicate | redevelopmentBegan |
P11886
|
FINISHED |
| Object | late 1980s |
—
|
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 1980s | Statement: [Canary Wharf, redevelopmentBegan, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopmentBegan Context triple: [Canary Wharf, redevelopmentBegan, late 1980s]
-
A.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
B.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
D.
reconstructionStart
Indicates the point in time or event at which a reconstruction process or activity begins.
-
E.
brokeGroundForRenovation
Indicates that an entity initiated construction work to renovate or significantly upgrade another entity or site.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.