Triple
T30095742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The RuSHA Case |
E764859
|
entity |
| Predicate | chargeCategory |
P71082
|
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: [The RuSHA Case, chargeCategory, war crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeCategory Context triple: [The RuSHA Case, chargeCategory, war crimes]
-
A.
chargeType
chosen
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
-
B.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
C.
chargeName
Indicates the specific name or label assigned to a charge or accusation associated with an entity.
-
D.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
E.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d90de4881909fa48ca060068046 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:07 p.m.