Triple
T30486262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingen nuclear power plant |
E775729
|
entity |
| Predicate | decommissioningStartYear |
P35722
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Lingen nuclear power plant, decommissioningStartYear, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissioningStartYear Context triple: [Lingen nuclear power plant, decommissioningStartYear, 1988]
-
A.
decommissioningStartDate
chosen
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
B.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
E.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:13 p.m.