Triple
T37536185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosecutor v. Bosco Ntaganda |
E933202
|
entity |
| Predicate | chargesInclude |
P69104
|
FINISHED |
| Object | war crimes |
—
|
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: war crimes | Statement: [Prosecutor v. Bosco Ntaganda, chargesInclude, war crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargesInclude Context triple: [Prosecutor v. Bosco Ntaganda, chargesInclude, war crimes]
-
A.
chargesIncluded
Indicates that the specified charges or fees are already accounted for and included within the referenced amount or agreement.
-
B.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
C.
containsCharge
chosen
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
D.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
E.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.