Triple
T24589502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grahame Park |
E608490
|
entity |
| Predicate | regenerationType |
P96762
|
FINISHED |
| Object | estate renewal |
—
|
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: estate renewal | Statement: [Grahame Park, regenerationType, estate renewal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regenerationType Context triple: [Grahame Park, regenerationType, estate renewal]
-
A.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
B.
hasRegenerationType
chosen
Indicates the specific kind or method of regeneration associated with an entity.
-
C.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
D.
regenerationAssociatedWith
Indicates an association between a regeneration process and a related factor, condition, or entity involved in or linked to that regenerative activity.
-
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.
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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.