Triple
T34978667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Eugene Prendergast |
E1008752
|
entity |
| Predicate | notableCourtOutcome |
P206778
|
FINISHED |
| Object | death sentence |
—
|
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: death sentence | Statement: [Patrick Eugene Prendergast, notableCourtOutcome, death sentence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCourtOutcome Context triple: [Patrick Eugene Prendergast, notableCourtOutcome, death sentence]
-
A.
notableSupremeCourtCase
Indicates that a legal case is recognized as a significant or influential decision by the Supreme Court.
-
B.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
C.
defendantInNotableTrial
Indicates that an entity served as the defendant in a trial that is considered notable or historically significant.
-
D.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
E.
courthouseNotability
Indicates that an entity is notable or significant specifically in relation to a courthouse (e.g., its history, events, or functions).
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.