Triple
T10170604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosecutor v. Théoneste Bagosora |
E235320
|
entity |
| Predicate | convictionBasis |
P42056
|
FINISHED |
| Object | command responsibility |
—
|
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: command responsibility | Statement: [Prosecutor v. Théoneste Bagosora, convictionBasis, command responsibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convictionBasis Context triple: [Prosecutor v. Théoneste Bagosora, convictionBasis, command responsibility]
-
A.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
B.
reasonForConviction
chosen
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
C.
convictionJurisdiction
Indicates the legal authority or geographic area under whose jurisdiction a conviction was issued.
-
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.
convictionStatusInOriginalTrial
Indicates whether an entity was found guilty or not guilty in the initial (original) court trial.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9d36608190be78665cc3410cf2 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.