Triple
T17080627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBMK-1000 |
E414458
|
entity |
| Predicate | postAccidentModification |
P34334
|
FINISHED |
| Object | control rod design changes |
—
|
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: control rod design changes | Statement: [RBMK-1000, postAccidentModification, control rod design changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postAccidentModification Context triple: [RBMK-1000, postAccidentModification, control rod design changes]
-
A.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
B.
resultOfAccident
chosen
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
C.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
D.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
-
E.
registrationStatusAfterAccident
Indicates the state of an entity’s registration following the occurrence of an accident.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.