Triple
T31562580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippsburg Nuclear Power Plant |
E805309
|
entity |
| Predicate | decommissioningProcessStart |
P35722
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Philippsburg Nuclear Power Plant, decommissioningProcessStart, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissioningProcessStart Context triple: [Philippsburg Nuclear Power Plant, decommissioningProcessStart, 2017]
-
A.
decommissioningStartDate
chosen
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
B.
decommissioningActivity
Indicates the process or actions involved in taking something out of service, shutting it down, or formally retiring it from use.
-
C.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
D.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
E.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:16 p.m.