Triple
T11794014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darlington Nuclear Generating Station |
E280458
|
entity |
| Predicate | reactor3Commissioned |
P101613
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Darlington Nuclear Generating Station, reactor3Commissioned, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactor3Commissioned Context triple: [Darlington Nuclear Generating Station, reactor3Commissioned, 1992]
-
A.
secondReactorCommissioned
Indicates that a second reactor at a facility has been formally brought into operational service.
-
B.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
C.
PM-3AReactorOperationalUntil
Indicates that a specific PM-3A reactor remained in an operational state up to a given point in time.
-
D.
PM-3AReactorOperationalFrom
Indicates that a PM-3A nuclear reactor was in an operational state starting from a specified point in time.
-
E.
reactor3StatusDuringAccident
Indicates the operational or physical condition of reactor 3 specifically during the time period of an accident.
- 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_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. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.