Triple
T12205699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRU reactor |
E290829
|
entity |
| Predicate | safetySystemUpgradeIssue |
P103393
|
FINISHED |
| Object | 2007 emergency power and pump upgrades dispute |
—
|
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: 2007 emergency power and pump upgrades dispute | Statement: [NRU reactor, safetySystemUpgradeIssue, 2007 emergency power and pump upgrades dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetySystemUpgradeIssue Context triple: [NRU reactor, safetySystemUpgradeIssue, 2007 emergency power and pump upgrades dispute]
-
A.
safetyIssueHighlighted
chosen
Indicates that a particular safety concern or hazard has been identified and explicitly brought to attention.
-
B.
safetyChangesImplemented
Indicates that specific safety-related modifications or measures have been put into effect.
-
C.
hasEmergencySystems
Indicates that the subject is equipped with or includes systems designed to detect, respond to, or manage emergency situations.
-
D.
safetyIssueBeforeRebuild
Indicates that a safety-related problem existed prior to a rebuild or reconstruction event.
-
E.
safetyRecordChangedAfter
Indicates that an entity’s safety record was modified following a specified event, time, or condition.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.