Triple
T11794012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darlington Nuclear Generating Station |
E280458
|
entity |
| Predicate | reactor1Commissioned |
P95776
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Darlington Nuclear Generating Station, reactor1Commissioned, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactor1Commissioned Context triple: [Darlington Nuclear Generating Station, reactor1Commissioned, 1990]
-
A.
secondReactorCommissioned
Indicates that a second reactor at a facility has been formally brought into operational service.
-
B.
firstReactorCommissioned
chosen
Indicates that the first reactor in a given context has been officially brought into operation or commissioned.
-
C.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
D.
reactor1StatusDuringAccident
Indicates the operational or physical condition of reactor 1 throughout the duration of an accident event.
-
E.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
- 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.