Triple
T11794028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darlington Nuclear Generating Station |
E280458
|
entity |
| Predicate | refurbishmentStart |
P27441
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Darlington Nuclear Generating Station, refurbishmentStart, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishmentStart Context triple: [Darlington Nuclear Generating Station, refurbishmentStart, 2016]
-
A.
renovationStart
chosen
Indicates the date or point in time when a renovation process begins.
-
B.
brokeGroundForRenovation
Indicates that an entity initiated construction work to renovate or significantly upgrade another entity or site.
-
C.
renovationPurpose
Indicates that an entity is being renovated with a specific intended goal, use, or outcome in mind.
-
D.
requiresRenovation
Indicates that an entity is in a condition that necessitates repair, updating, or refurbishment before it is suitable for normal use or standards.
-
E.
renovationPeriod
Indicates the time span during which an object, structure, or entity undergoes renovation or refurbishment.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.