Triple
T30527767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barking Riverside |
E776903
|
entity |
| Predicate | regenerationArea |
P169826
|
FINISHED |
| Object | Thames Gateway |
—
|
NE NERFINISHED |
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: Thames Gateway | Statement: [Barking Riverside, regenerationArea, Thames Gateway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regenerationArea Context triple: [Barking Riverside, regenerationArea, Thames Gateway]
-
A.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
B.
regenerationAssociatedWith
Indicates an association between a regeneration process and a related factor, condition, or entity involved in or linked to that regenerative activity.
-
C.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
D.
regenerationContinuedIn
Indicates that an ongoing process of regeneration persists or is maintained within a specified context, location, or time period.
-
E.
regenerationSource
Indicates that one entity serves as the origin, cause, or provider for the restoration or regrowth of another entity.
- F. None of above. chosen
Provenance (4 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68849c7fc81908b8dcb4b108c6b8a |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:17 p.m.