Triple
T22806936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 3 (nuclear) |
E564561
|
entity |
| Predicate | spentFuelStorage |
P78474
|
FINISHED |
| Object | independent spent fuel storage installation |
—
|
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: independent spent fuel storage installation | Statement: [Unit 3 (nuclear), spentFuelStorage, independent spent fuel storage installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spentFuelStorage Context triple: [Unit 3 (nuclear), spentFuelStorage, independent spent fuel storage installation]
-
A.
spentFuelPoolLocation
Indicates the physical place where a spent fuel pool is situated or housed.
-
B.
spentFuelDestination
Indicates where spent fuel is sent or stored after it has been used.
-
C.
hasIndependentSpentFuelStorageInstallation
chosen
Indicates that an entity possesses a separate, dedicated facility or installation for storing spent (used) nuclear fuel independently of other storage systems.
-
D.
spentFuelRemovalStartDate
Indicates the date on which the process of removing spent (used) fuel from a facility or system begins.
-
E.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5d41dc819081912d9e29828bfb |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.