Triple
T18053662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in Motal |
E431981
|
entity |
| Predicate | natureOfAtrocity |
P95406
|
FINISHED |
| Object | systematic persecution |
—
|
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: systematic persecution | Statement: [Holocaust in Motal, natureOfAtrocity, systematic persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfAtrocity Context triple: [Holocaust in Motal, natureOfAtrocity, systematic persecution]
-
A.
natureOfAtrocities
chosen
Indicates the specific type or character of atrocities associated with an event, action, or entity.
-
B.
timeOfMassViolence
Indicates the specific time at which an act or event of mass violence occurred.
-
C.
warCrimesContext
Indicates a context in which actions or events are associated with the commission, investigation, or adjudication of war crimes.
-
D.
associatedWithCrimesAgainstHumanity
Indicates a relationship in which an entity is linked or connected to the planning, commission, support, or responsibility for crimes against humanity.
-
E.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c100e7e4819084470c5b7fced334 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.