Triple
T9709479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 4 |
E234984
|
entity |
| Predicate | spentFuelAssembliesRemoved |
P88230
|
FINISHED |
| Object | 1533 |
—
|
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: 1533 | Statement: [Fukushima Daiichi Unit 4, spentFuelAssembliesRemoved, 1533]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spentFuelAssembliesRemoved Context triple: [Fukushima Daiichi Unit 4, spentFuelAssembliesRemoved, 1533]
-
A.
numberOfFuelAssemblies
chosen
Indicates the total count of fuel assemblies associated with or contained in a given system, component, or facility.
-
B.
fuelCladding
Indicates a relationship where a material or component serves as the cladding (protective outer layer) for nuclear fuel.
-
C.
aimedToBeDismantledBy
Indicates that one entity was the intended target of dismantling or disassembly by another entity.
-
D.
decommissioningActivity
Indicates the process or actions involved in taking something out of service, shutting it down, or formally retiring it from use.
-
E.
claimedDecommissioningOfWeapons
Indicates that an entity has asserted or reported that certain weapons have been taken out of service or rendered non-operational.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.