Triple
T37155461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dounreay |
E920484
|
entity |
| Predicate | firstReactorCriticality |
P187214
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Dounreay, firstReactorCriticality, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReactorCriticality Context triple: [Dounreay, firstReactorCriticality, 1959]
-
A.
PrototypeFastReactorCriticality
chosen
Indicates that a prototype fast nuclear reactor has reached a self-sustaining chain reaction (critical) state.
-
B.
firstCriticalityUnit1
Indicates that the entity is associated with the first unit or level of criticality, specifically labeled as "unit 1."
-
C.
firstCriticalityUnit2
Indicates that the referenced entity is the second unit or component associated with the first level or category of criticality.
-
D.
criticality
Indicates the degree of importance, urgency, or potential impact associated with an entity, condition, or situation within a given context.
-
E.
criticalityAccident
Indicates an event in which a nuclear chain reaction becomes unintentionally self-sustaining or supercritical, leading to a hazardous release of radiation or energy.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.