Triple
T33060527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novovoronezh Nuclear Power Plant |
E845962
|
entity |
| Predicate | numberOfUnitsDecommissioned |
P203904
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Novovoronezh Nuclear Power Plant, numberOfUnitsDecommissioned, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfUnitsDecommissioned Context triple: [Novovoronezh Nuclear Power Plant, numberOfUnitsDecommissioned, 5]
-
A.
allUnitsDecommissionedBy
Indicates that every unit within a specified set has been decommissioned by a particular agent or entity.
-
B.
decommissionedFromUSN
Indicates that something was formally retired or removed from active service in the United States Navy.
-
C.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
D.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
E.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_6a024936acc48190bc4a9abe4c519302 |
completed | May 11, 2026, 9:25 p.m. |
Created at: May 1, 2026, 1:25 a.m.