Triple
T17080581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reactor No. 4 |
E414457
|
entity |
| Predicate | operatorAtTimeOfAccident |
P106885
|
FINISHED |
| Object | Chernobyl Nuclear Power Plant staff |
—
|
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: Chernobyl Nuclear Power Plant staff | Statement: [Reactor No. 4, operatorAtTimeOfAccident, Chernobyl Nuclear Power Plant staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAtTimeOfAccident Context triple: [Reactor No. 4, operatorAtTimeOfAccident, Chernobyl Nuclear Power Plant staff]
-
A.
principalOperatorAtTimeOfAccident
chosen
Indicates that an entity was the main person operating or controlling something at the specific time when an accident occurred.
-
B.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
E.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
- 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.