Triple
T28305657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yusef Salaam |
E713836
|
entity |
| Predicate | exonerationReason |
P93712
|
FINISHED |
| Object | DNA evidence excluding him |
—
|
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: DNA evidence excluding him | Statement: [Yusef Salaam, exonerationReason, DNA evidence excluding him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exonerationReason Context triple: [Yusef Salaam, exonerationReason, DNA evidence excluding him]
-
A.
exoneratedIn
Indicates that an entity has been officially cleared of blame or legal responsibility in a particular case, situation, or proceeding.
-
B.
dateOfExoneration
Indicates the date on which an entity was officially cleared of blame, guilt, or conviction.
-
C.
reasonForOverturningConviction
chosen
Indicates the specific grounds or justification that led to a prior conviction being reversed or nullified.
-
D.
reasonForRelief
Indicates the cause, justification, or circumstance that explains why relief or alleviation from a condition or obligation occurs.
-
E.
pardonReason
Indicates the reason or justification for which a pardon is granted.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:37 p.m.