Triple
T9314173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Justice Act 1967 |
E224076
|
entity |
| Predicate | introducedParoleSystem |
P88037
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Criminal Justice Act 1967, introducedParoleSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedParoleSystem Context triple: [Criminal Justice Act 1967, introducedParoleSystem, yes]
-
A.
eventuallyParoled
Indicates that an individual who was previously incarcerated was later released from prison on parole.
-
B.
posthumousPardonGrantedBy
Indicates that a formal pardon was granted to an individual after their death by a specified authority or institution.
-
C.
deathSentenceCommutedBy
Indicates that a previously imposed death sentence on an individual is officially reduced or replaced with a lesser punishment by a specified authority.
-
D.
pardonOrClemencyBy
Indicates that an authority grants a pardon or clemency to someone, forgiving or reducing their legal penalties.
-
E.
restrictionAfterPardon
Indicates that a restriction or limitation is imposed on an entity following the granting of a pardon.
- F. None of above. chosen
Provenance (4 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.