Triple
T13933733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernobyl Nuclear Power Plant |
E335055
|
entity |
| Predicate | reactor2CommissioningDate |
P95777
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [Chernobyl Nuclear Power Plant, reactor2CommissioningDate, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactor2CommissioningDate Context triple: [Chernobyl Nuclear Power Plant, reactor2CommissioningDate, 1978]
-
A.
secondReactorCommissioned
chosen
Indicates that a second reactor at a facility has been formally brought into operational service.
-
B.
reactor3Commissioned
Indicates that the third reactor in a series or facility has been officially placed into service or begun operation.
-
C.
reactor4Commissioned
Indicates that the fourth reactor unit has been officially placed into service and begun operational use.
-
D.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
E.
firstReactorCommissioned
Indicates that the first reactor in a given context has been officially brought into operation or commissioned.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf28df081908d897d7b9ec7939d |
completed | April 14, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.