Triple
T9446831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 2 |
E227784
|
entity |
| Predicate | plannedFuelDebrisRetrievalStart |
P88232
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [Fukushima Daiichi Unit 2, plannedFuelDebrisRetrievalStart, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFuelDebrisRetrievalStart Context triple: [Fukushima Daiichi Unit 2, plannedFuelDebrisRetrievalStart, 2020s]
-
A.
ascentStageJettisonDate
Indicates the date on which the ascent stage of a spacecraft is separated or discarded.
-
B.
lastMissionLandingPlannedDate
Indicates the scheduled calendar date on which the final mission in a series is planned to land.
-
C.
orbitInsertionDate
Indicates the date on which an object is placed into its designated orbit.
-
D.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
E.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f35394c8190aa77528dabd6139c |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:51 p.m.