Triple
T37775086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babi Yar |
E941660
|
entity |
| Predicate | laterCrimeConcealment |
P169062
|
FINISHED |
| Object | exhumation and burning of bodies by Nazis in 1943 |
—
|
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: exhumation and burning of bodies by Nazis in 1943 | Statement: [Babi Yar, laterCrimeConcealment, exhumation and burning of bodies by Nazis in 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCrimeConcealment Context triple: [Babi Yar, laterCrimeConcealment, exhumation and burning of bodies by Nazis in 1943]
-
A.
triesToConcealCrimeFrom
chosen
Indicates an attempt by one entity to hide, obscure, or prevent another entity from discovering or becoming aware of a crime.
-
B.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
C.
crimeAgainst
Indicates that one entity commits or is responsible for a criminal act directed toward another entity.
-
D.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
E.
commitsCrimeIn
Indicates that an entity carries out or is responsible for a criminal act within a specified location or jurisdiction.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
Created at: May 3, 2026, 4:19 p.m.