Triple
T25597606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron McKinney |
E641695
|
entity |
| Predicate | pleaOrVerdict |
P9727
|
FINISHED |
| Object | convicted by jury |
—
|
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: convicted by jury | Statement: [Aaron McKinney, pleaOrVerdict, convicted by jury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pleaOrVerdict Context triple: [Aaron McKinney, pleaOrVerdict, convicted by jury]
-
A.
verdict
chosen
Indicates the formal decision or judgment reached and declared at the conclusion of a legal or evaluative process.
-
B.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
C.
pleaTo
Indicates that one entity formally requests or appeals to another entity, often seeking a specific decision, action, or lenient judgment.
-
D.
pleadsWith
Indicates that one entity urgently and emotionally appeals to another, often requesting help, mercy, or a favorable decision.
-
E.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
- 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_69f5f9a420f08190a8ed8c9a8c245fc4 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:28 p.m.