Triple
T24254595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwolle labor camp |
E603632
|
entity |
| Predicate | persecutor |
P20070
|
FINISHED |
| Object | Nazi regime |
—
|
NE NERFINISHED |
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: Nazi regime | Statement: [Zwolle labor camp, persecutor, Nazi regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persecutor Context triple: [Zwolle labor camp, persecutor, Nazi regime]
-
A.
persecutes
chosen
Indicates that one entity persistently harasses, oppresses, or inflicts suffering on another, often in an unjust or hostile manner.
-
B.
persecutorOfMother
Indicates that one entity persecutes, harasses, or oppresses another entity who is the mother of someone.
-
C.
persecutionOf
Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
-
D.
mainPersecutor
Indicates that one entity is the primary agent responsible for persecuting or oppressing another entity.
-
E.
perpetratorType
Indicates the classification or category of the entity that carried out or is responsible for a harmful, illegal, or otherwise wrongful act.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8ca4988190b565c2873dc6559d |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.