Triple
T33060541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novovoronezh Nuclear Power Plant |
E845962
|
entity |
| Predicate | statusOfUnit5 |
P66640
|
FINISHED |
| Object | decommissioned |
—
|
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: decommissioned | Statement: [Novovoronezh Nuclear Power Plant, statusOfUnit5, decommissioned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfUnit5 Context triple: [Novovoronezh Nuclear Power Plant, statusOfUnit5, decommissioned]
-
A.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
statusOfSubunit
chosen
Indicates the current condition, state, or operational situation of a component or subunit in relation to its larger whole.
-
D.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
E.
statusInSystem7
Indicates that an entity holds a particular status or state within the context of system 7.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.