Triple
T13065571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Baer |
E329312
|
entity |
| Predicate | trialStatus |
P39428
|
FINISHED |
| Object | died in custody before verdict |
—
|
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: died in custody before verdict | Statement: [Richard Baer, trialStatus, died in custody before verdict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialStatus Context triple: [Richard Baer, trialStatus, died in custody before verdict]
-
A.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
-
B.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
C.
defendantStatus
chosen
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
D.
appealStatus
Indicates the current state or outcome of an appeal within a review or decision process.
-
E.
judicialReviewStatus
Indicates whether and how a decision, action, or law has been or can be examined, challenged, or ruled upon by a judicial authority.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980eb81948190b27eb9ae19978079 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:59 p.m.