Triple
T19281786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilibino Nuclear Power Plant |
E482205
|
entity |
| Predicate | lastReactorCommissioned |
P135438
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Bilibino Nuclear Power Plant, lastReactorCommissioned, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastReactorCommissioned Context triple: [Bilibino Nuclear Power Plant, lastReactorCommissioned, 1977]
-
A.
firstReactorCommissioned
Indicates that the first reactor in a given context has been officially brought into operation or commissioned.
-
B.
reactor3CommissioningDate
Indicates the date on which the third reactor in a series was formally commissioned and entered into operational service.
-
C.
secondReactorCommissioned
Indicates that a second reactor at a facility has been formally brought into operational service.
-
D.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
- 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_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. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:30 p.m.