Triple
T31884541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office for Nuclear Regulation |
E813970
|
entity |
| Predicate | canProsecuteFor |
P113668
|
FINISHED |
| Object | breaches of nuclear safety law |
—
|
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: breaches of nuclear safety law | Statement: [Office for Nuclear Regulation, canProsecuteFor, breaches of nuclear safety law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canProsecuteFor Context triple: [Office for Nuclear Regulation, canProsecuteFor, breaches of nuclear safety law]
-
A.
mayProsecute
chosen
Indicates that one party has the legal authority or permission to initiate and conduct prosecution against another party.
-
B.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
-
C.
canBeSuedAs
Indicates that one entity has legal standing or capacity to be the target of a lawsuit initiated by another entity.
-
D.
helpsProsecute
Indicates that one entity assists another entity in carrying out a legal prosecution against a target.
-
E.
canIssueWrits
Indicates that an entity has the legal authority to issue formal writs or orders.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0daa4988190b78498e7da6a30dd |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:57 p.m.