Triple
T25597728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murder of James Byrd Jr. |
E641698
|
entity |
| Predicate | legalOutcomeForShawnAllenBerry |
P2931
|
FINISHED |
| Object | life imprisonment |
—
|
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: life imprisonment | Statement: [Murder of James Byrd Jr., legalOutcomeForShawnAllenBerry, life imprisonment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalOutcomeForShawnAllenBerry Context triple: [Murder of James Byrd Jr., legalOutcomeForShawnAllenBerry, life imprisonment]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
laterJudgedByStevens
Indicates that the subject was subsequently evaluated, ruled on, or otherwise formally judged by an individual or authority named Stevens.
-
C.
wasOverturnedByCourt
Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
-
D.
wasOverturnedInYear
Indicates that a prior decision, ruling, or outcome was reversed or nullified in the specified year.
-
E.
outcomeForKathrynAPiper
Indicates the result, consequence, or effect that something has specifically for Kathryn A. Piper.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 4:29 p.m.