Triple
T37423531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeremy Bamber |
E929925
|
entity |
| Predicate | appealedConviction |
P10643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jeremy Bamber, appealedConviction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealedConviction Context triple: [Jeremy Bamber, appealedConviction, yes]
-
A.
appealCondemned
Indicates that an appeal has been rejected, dismissed, or otherwise not upheld by the deciding authority.
-
B.
convictionQuashed
Indicates that a previously imposed criminal conviction has been formally annulled or set aside, so it no longer has legal effect.
-
C.
reasonForOverturningConviction
Indicates the specific grounds or justification that led to a prior conviction being reversed or nullified.
-
D.
appeal
chosen
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
E.
convictedAs
Indicates that a person has been formally found guilty and sentenced in a specific role or capacity (e.g., as a particular type of offender) in a legal proceeding.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.