Triple
T15131227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssele nuclear power plant |
E361423
|
entity |
| Predicate | hasEmergencyPowerSupply |
P10326
|
FINISHED |
| Object | diesel generators |
—
|
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: diesel generators | Statement: [Borssele nuclear power plant, hasEmergencyPowerSupply, diesel generators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyPowerSupply Context triple: [Borssele nuclear power plant, hasEmergencyPowerSupply, diesel generators]
-
A.
hasEmergencySystems
Indicates that the subject is equipped with or includes systems designed to detect, respond to, or manage emergency situations.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
emergencyPower
chosen
Indicates that an entity has backup or auxiliary power available or activated for use during emergencies or primary power failures.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
hasEmergencyAlarm
Indicates that an entity is equipped with or associated with an emergency alarm system that can be activated in urgent situations.
- 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.