Triple
T31016291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daini Nuclear Power Plant |
E790334
|
entity |
| Predicate | commercialOperationStartUnit4 |
P179514
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Fukushima Daini Nuclear Power Plant, commercialOperationStartUnit4, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialOperationStartUnit4 Context triple: [Fukushima Daini Nuclear Power Plant, commercialOperationStartUnit4, 1987]
-
A.
commercialOperationStartUnit1
Indicates the date or time when commercial operation of Unit 1 begins.
-
B.
commercialOperationStartUnit3
Indicates the point in time when the third unit of a facility or system begins its commercial operation.
-
C.
commercialOperationStartUnit2
Indicates the point in time when the second unit of a facility or system begins its commercial operation.
-
D.
commercialOperation
Indicates that an entity is engaged in or associated with a profit-oriented business activity or transaction.
-
E.
commercialOperator
Indicates that an entity operates or manages a commercial activity, service, or facility, typically for profit or business purposes.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 29, 2026, 8:57 p.m.