Triple
T4185526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Pile-2 |
E88301
|
entity |
| Predicate | decommissioning |
P14100
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Chicago Pile-2, decommissioning, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissioning Context triple: [Chicago Pile-2, decommissioning, 1954]
-
A.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
B.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
C.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
D.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
demobilization
Indicates the process by which armed forces or combatants are formally released from military service and military structures are reduced or disbanded.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.