Triple
T4703977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L Reactor |
E104343
|
entity |
| Predicate | deactivationStart |
P35722
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [L Reactor, deactivationStart, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivationStart Context triple: [L Reactor, deactivationStart, late 1980s]
-
A.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
B.
decommissioningStartDate
chosen
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
C.
ceasedActivityUnder
Indicates that an entity stopped performing a particular activity while under the authority, influence, or conditions imposed by another entity.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.