Triple
T31032245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 4 reactor building |
E790757
|
entity |
| Predicate | spentFuelRemovedTo |
P90381
|
FINISHED |
| Object | common spent fuel pool at Fukushima Daiichi |
—
|
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: common spent fuel pool at Fukushima Daiichi | Statement: [Unit 4 reactor building, spentFuelRemovedTo, common spent fuel pool at Fukushima Daiichi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spentFuelRemovedTo Context triple: [Unit 4 reactor building, spentFuelRemovedTo, common spent fuel pool at Fukushima Daiichi]
-
A.
spentFuelRemovalStartDate
Indicates the date on which the process of removing spent (used) fuel from a facility or system begins.
-
B.
spentFuelDestination
chosen
Indicates where spent fuel is sent or stored after it has been used.
-
C.
spentFuelPoolLocation
Indicates the physical place where a spent fuel pool is situated or housed.
-
D.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:59 p.m.