Triple
T31016303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daini Nuclear Power Plant |
E790334
|
entity |
| Predicate | longTermStatusAfter2011 |
P75870
|
FINISHED |
| Object | shutdown |
—
|
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: shutdown | Statement: [Fukushima Daini Nuclear Power Plant, longTermStatusAfter2011, shutdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longTermStatusAfter2011 Context triple: [Fukushima Daini Nuclear Power Plant, longTermStatusAfter2011, shutdown]
-
A.
statusAfter2011
chosen
Indicates the condition or state of an entity specifically in the period following the year 2011.
-
B.
legalStatusAfter2011
Indicates the legal status or condition that applies to an entity starting from the year 2011 onward.
-
C.
statusAfter2010
Indicates the condition or state of an entity specifically in the period after the year 2010.
-
D.
legalStatusAfter2009
Indicates the legal status or condition that an entity holds from the year 2009 onward, typically reflecting changes due to laws or regulations taking effect at or after that time.
-
E.
legalStatusAfter1801
Indicates the legal status or condition of an entity as it existed or was defined after the year 1801.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.