Triple
T22806923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 3 (nuclear) |
E564561
|
entity |
| Predicate | permanentShutdownYear |
P19867
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Unit 3 (nuclear), permanentShutdownYear, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentShutdownYear Context triple: [Unit 3 (nuclear), permanentShutdownYear, 1976]
-
A.
plannedShutdownYear
Indicates the year in which an entity is scheduled or planned to be shut down or taken out of operation.
-
B.
permanentShutdown
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
C.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
D.
closureYear
chosen
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
E.
hasDiscontinuationApproxYear
Indicates that an entity ceased to exist, operate, or be available around a specified (approximate) calendar year.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5d41dc819081912d9e29828bfb |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.