Triple
T14172684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Burrows |
E351250
|
entity |
| Predicate | wronglyConvictedOf |
P63058
|
FINISHED |
| Object | murder of Terrence Steadman |
—
|
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: murder of Terrence Steadman | Statement: [Lincoln Burrows, wronglyConvictedOf, murder of Terrence Steadman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wronglyConvictedOf Context triple: [Lincoln Burrows, wronglyConvictedOf, murder of Terrence Steadman]
-
A.
wronglyConvictedPerson
chosen
Indicates that a person has been found guilty and convicted of a crime they did not actually commit.
-
B.
wronglyConvictedGroup
Indicates that a group of entities has been convicted of an offense despite the conviction being incorrect or unjust.
-
C.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
-
D.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
E.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.