Triple
T4744626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totenkopf Division |
E105329
|
entity |
| Predicate | perpetratorIn |
P698
|
FINISHED |
| Object | atrocities on the Eastern Front |
—
|
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: atrocities on the Eastern Front | Statement: [Totenkopf Division, perpetratorIn, atrocities on the Eastern Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorIn Context triple: [Totenkopf Division, perpetratorIn, atrocities on the Eastern Front]
-
A.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
B.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
C.
perpetratorNationality
Indicates the country or nationality to which a perpetrator of an act, crime, or harmful event belongs.
-
D.
perpetratorAbbreviation
Indicates that one entity is an abbreviated or shortened form used to refer to the perpetrator of an action or offense.
-
E.
perpetratorAllegiance
Indicates that the perpetrator is affiliated with, loyal to, or acting on behalf of a particular group, organization, or cause.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64aa72c0819082ede0f531d75e65 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.