Triple
T9757083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Nuclear Power Plant |
E236578
|
entity |
| Predicate | onSiteDryCaskStorage |
P90842
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Salem Nuclear Power Plant, onSiteDryCaskStorage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onSiteDryCaskStorage Context triple: [Salem Nuclear Power Plant, onSiteDryCaskStorage, yes]
-
A.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
B.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for another entity.
-
C.
canDryOut
Indicates that one entity has the ability or tendency to cause another entity to lose moisture and become dry.
-
D.
storageInterface
Indicates that one entity serves as a storage interface used by or associated with another entity for storing or retrieving data.
-
E.
supportsOnlineDefragmentation
Indicates that the subject provides the capability to perform defragmentation operations while remaining online and operational.
- F. None of above. chosen
Provenance (4 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda046a4048190a2c66321a9911817 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:24 p.m.