Triple
T19281794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilibino Nuclear Power Plant |
E482205
|
entity |
| Predicate | reactorDecommissioningStart |
P35722
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Bilibino Nuclear Power Plant, reactorDecommissioningStart, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorDecommissioningStart Context triple: [Bilibino Nuclear Power Plant, reactorDecommissioningStart, 2019]
-
A.
decommissioningActivity
Indicates the process or actions involved in taking something out of service, shutting it down, or formally retiring it from use.
-
B.
estimatedDecommissioningDuration
Indicates the expected length of time required to complete the decommissioning process of an entity.
-
C.
decommissioningStartDate
chosen
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
D.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
E.
reactor3Commissioned
Indicates that the third reactor in a series or facility has been officially placed into service or begun operation.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.