Triple
T15131220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssele nuclear power plant |
E361423
|
entity |
| Predicate | safetyUpgradesImplemented |
P33946
|
FINISHED |
| Object | post-Fukushima safety improvements |
—
|
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: post-Fukushima safety improvements | Statement: [Borssele nuclear power plant, safetyUpgradesImplemented, post-Fukushima safety improvements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyUpgradesImplemented Context triple: [Borssele nuclear power plant, safetyUpgradesImplemented, post-Fukushima safety improvements]
-
A.
safetyChangesImplemented
chosen
Indicates that specific safety-related modifications or measures have been put into effect.
-
B.
hasSafetyInfrastructure
Indicates that appropriate safety-related structures, systems, or measures are present for the referenced entity or environment.
-
C.
measuresSafetyUsing
Indicates that an entity evaluates or assesses safety by employing a specified method, tool, or standard.
-
D.
safetyRecordChangedAfter
Indicates that an entity’s safety record was modified following a specified event, time, or condition.
-
E.
safetyRatingHighlight
Indicates that an entity’s safety rating is emphasized or specially marked as noteworthy compared to others.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.