Triple
T11920028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinkley Point A nuclear power station |
E283628
|
entity |
| Predicate | shutDown |
P11821
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Hinkley Point A nuclear power station, shutDown, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shutDown Context triple: [Hinkley Point A nuclear power station, shutDown, 2000]
-
A.
shutdownCapability
Indicates the ability or permission for one entity to power off, deactivate, or terminate the operation of another entity or system.
-
B.
permanentShutdown
chosen
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
C.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
D.
designedToAllowShutdownOf
Indicates that one entity is specifically created or configured to enable the shutdown or power-off of another entity.
-
E.
firstLongShutdown
Indicates the first occurrence of a prolonged shutdown event affecting the referenced entity or system.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.