Triple
T14730952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Georg Thierack |
E346070
|
entity |
| Predicate | statusDuringTrial |
P47971
|
FINISHED |
| Object | committed suicide 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: committed suicide before verdict | Statement: [Otto Georg Thierack, statusDuringTrial, committed suicide before verdict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringTrial Context triple: [Otto Georg Thierack, statusDuringTrial, committed suicide before verdict]
-
A.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
-
B.
governingAuthorityDuringTrial
Indicates the authority or body that held legal or political control over the proceedings during a specific trial.
-
C.
judgeInTrial
Indicates that an entity serves as the judicial authority presiding over and making legal determinations in a specific trial.
-
D.
statusInJudges
Indicates that an entity holds a particular role, position, or standing within a group or body of judges.
-
E.
outcomeOfTrial
chosen
Indicates that a particular result or verdict is produced as the consequence of a specific trial or 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26311c8819093a81ff0fa43b33b |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.