Triple
T9583244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 3 |
E231223
|
entity |
| Predicate | remoteDebrisRemoval |
P30695
|
FINISHED |
| Object | used remote-controlled equipment for rubble removal |
—
|
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: used remote-controlled equipment for rubble removal | Statement: [Fukushima Daiichi Unit 3, remoteDebrisRemoval, used remote-controlled equipment for rubble removal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remoteDebrisRemoval Context triple: [Fukushima Daiichi Unit 3, remoteDebrisRemoval, used remote-controlled equipment for rubble removal]
-
A.
damRemovalProject
Indicates a project or initiative undertaken to remove, dismantle, or decommission a dam.
-
B.
debrisRecoveryEffort
chosen
Indicates efforts or actions undertaken to locate, collect, and secure debris resulting from an incident or event.
-
C.
aimedToBeDismantledBy
Indicates that one entity was the intended target of dismantling or disassembly by another entity.
-
D.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
E.
demolitionMethod
Indicates the technique or process used to carry out a demolition.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cebaf081908033536a53fbf668 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.