Triple
T31307695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis–Besse Nuclear Power Station |
E798377
|
entity |
| Predicate | hasSafetyIssue |
P103393
|
FINISHED |
| Object | reactor vessel head corrosion |
—
|
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: reactor vessel head corrosion | Statement: [Davis–Besse Nuclear Power Station, hasSafetyIssue, reactor vessel head corrosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyIssue Context triple: [Davis–Besse Nuclear Power Station, hasSafetyIssue, reactor vessel head corrosion]
-
A.
safetyIssueHighlighted
chosen
Indicates that a particular safety concern or hazard has been identified and explicitly brought to attention.
-
B.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
C.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
D.
hasCertificationIssueIn
Indicates that an entity has a certification-related problem, defect, or noncompliance occurring within a specified context, scope, or location.
-
E.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced entity.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 9:14 p.m.