Triple
T9446840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 2 |
E227784
|
entity |
| Predicate | gridStatusAfterAccident |
P34334
|
FINISHED |
| Object | disconnected from grid |
—
|
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: disconnected from grid | Statement: [Fukushima Daiichi Unit 2, gridStatusAfterAccident, disconnected from grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridStatusAfterAccident Context triple: [Fukushima Daiichi Unit 2, gridStatusAfterAccident, disconnected from grid]
-
A.
accidentPhase
Indicates the specific stage or phase of progression within an accident or incident event.
-
B.
resultOfAccident
chosen
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
C.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
D.
accidentSeverity
Indicates the level or degree of seriousness associated with an accident.
-
E.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
- 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_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. |
Created at: March 30, 2026, 7:51 p.m.