Triple
T4639315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R Reactor |
E101611
|
entity |
| Predicate | decommissioningStart |
P35722
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [R Reactor, decommissioningStart, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissioningStart Context triple: [R Reactor, decommissioningStart, 1960s]
-
A.
decommissioningStartDate
chosen
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
B.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
E.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8e0ee88190becab97d2ef1571a |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.