Triple
T5477998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restricted Data |
E123401
|
entity |
| Predicate | violationsPunishedBy |
P36372
|
FINISHED |
| Object | criminal penalties |
—
|
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: criminal penalties | Statement: [Restricted Data, violationsPunishedBy, criminal penalties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violationsPunishedBy Context triple: [Restricted Data, violationsPunishedBy, criminal penalties]
-
A.
violationConsequences
chosen
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
D.
violationsSearchedIn
Indicates that an entity has been examined or queried specifically to identify potential violations or breaches.
-
E.
allegedViolationSystem
Indicates a system is reported or suspected to have violated a rule, policy, or regulation, without the violation being legally or formally established.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd92460f008190bf9d64ddd9c507a7 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.