Triple
T15131205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssele nuclear power plant |
E361423
|
entity |
| Predicate | plannedShutdownYear |
P117437
|
FINISHED |
| Object | 2033 |
—
|
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: 2033 | Statement: [Borssele nuclear power plant, plannedShutdownYear, 2033]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedShutdownYear Context triple: [Borssele nuclear power plant, plannedShutdownYear, 2033]
-
A.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
B.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
C.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
D.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
E.
originalPlannedOpeningYear
Indicates the year that was initially scheduled or intended for something to open, before any delays or changes.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.