Triple
T21773174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiwis |
E537485
|
entity |
| Predicate | victimGroupOfRecruitment |
P87855
|
FINISHED |
| Object | Soviet POWs under coercive conditions |
—
|
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: Soviet POWs under coercive conditions | Statement: [Hiwis, victimGroupOfRecruitment, Soviet POWs under coercive conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimGroupOfRecruitment Context triple: [Hiwis, victimGroupOfRecruitment, Soviet POWs under coercive conditions]
-
A.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
B.
victimGroupContext
chosen
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
-
C.
victimGroupHelped
Indicates that assistance, support, or aid was provided to a group identified as victims.
-
D.
victimGroupAssisted
Indicates that assistance, support, or aid is provided to a group identified as victims.
-
E.
victimCategory
Indicates the classification or type of victim associated with an event, action, or harmful outcome.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031b0ce28819093a891f50a77dfc6 |
completed | April 28, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.