Triple
T32884862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alton Estate |
E841168
|
entity |
| Predicate | hasRegenStatus |
—
|
GENERATED |
| Object | subject to regeneration proposals |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegenStatus Context triple: [Alton Estate, hasRegenStatus, subject to regeneration proposals]
-
A.
hasRegenerationStatus
chosen
Indicates the current state or condition of an entity’s regeneration process (e.g., whether and how it is being restored or renewed).
-
B.
hasRegenerationType
Indicates the specific kind or method of regeneration associated with an entity.
-
C.
hasRegenerationCycleWith
Indicates that two entities are linked by a recurring regeneration or renewal process that they undergo together or in relation to each other.
-
D.
hasMultipleRegenerations
Indicates that an entity has undergone more than one process of regeneration or renewal.
-
E.
canRegenerate
Indicates that an entity has the ability to regrow or restore lost or damaged parts of itself.
- F. None of above.
Provenance (1 batch)
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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:18 a.m.