Triple
T12205673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRU reactor |
E290829
|
entity |
| Predicate | permanentShutdownDate |
P92642
|
FINISHED |
| Object | 2018-03-31 |
—
|
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: 2018-03-31 | Statement: [NRU reactor, permanentShutdownDate, 2018-03-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentShutdownDate Context triple: [NRU reactor, permanentShutdownDate, 2018-03-31]
-
A.
finalShutdownDate
chosen
Indicates the date on which an entity is permanently shut down or ceases operation.
-
B.
permanentClosureAnnouncementDate
Indicates the date on which an official announcement was made that something (such as a facility, service, or location) will be permanently closed.
-
C.
permanentShutdown
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
D.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.