Triple
T3938106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Dock |
E90962
|
entity |
| Predicate | regeneration |
P49259
|
FINISHED |
| Object | 1980s urban renewal project |
—
|
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: 1980s urban renewal project | Statement: [Albert Dock, regeneration, 1980s urban renewal project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regeneration Context triple: [Albert Dock, regeneration, 1980s urban renewal project]
-
A.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
B.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
C.
regenerationContinuedIn
chosen
Indicates that an ongoing process of regeneration persists or is maintained within a specified context, location, or time period.
-
D.
regenerationRetcon
Indicates a continuity-altering change where a character’s regeneration or renewal is retroactively modified, redefined, or overwritten in the narrative.
-
E.
featuresRegeneration
Indicates that an entity possesses the ability to regenerate or regrow lost or damaged parts.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.