Triple
T37155464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dounreay |
E920484
|
entity |
| Predicate | DounreayFastReactorShutdown |
P187484
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Dounreay, DounreayFastReactorShutdown, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DounreayFastReactorShutdown Context triple: [Dounreay, DounreayFastReactorShutdown, 1977]
-
A.
DounreayFastReactorCriticality
Indicates that the Dounreay Fast Reactor is in a state of nuclear criticality, sustaining a self-sustaining chain reaction.
-
B.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
C.
nuclearReactorRemoved
Indicates that a nuclear reactor has been taken out of service and physically removed from its previous location or installation.
-
D.
numberOfFuelAssembliesInSpentFuelPoolAtAccident
Indicates the quantity of fuel assemblies that were present in the spent fuel pool at the time of the accident.
-
E.
plutoniumFacility
Indicates a facility that is involved in the production, processing, handling, or storage of plutonium.
- F. None of above. chosen
Provenance (4 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.