Triple
T31032244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 4 reactor building |
E790757
|
entity |
| Predicate | spentFuelRemovalEndDate |
P96281
|
FINISHED |
| Object | 2014-12-20 |
—
|
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: 2014-12-20 | Statement: [Unit 4 reactor building, spentFuelRemovalEndDate, 2014-12-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spentFuelRemovalEndDate Context triple: [Unit 4 reactor building, spentFuelRemovalEndDate, 2014-12-20]
-
A.
spentFuelRemovalStartDate
Indicates the date on which the process of removing spent (used) fuel from a facility or system begins.
-
B.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
C.
withdrawalEnd
chosen
Indicates the point in time or condition at which a withdrawal process or right comes to an end.
-
D.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694c2fe008190b643a2b2d8274669 |
completed | May 3, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.