Triple
T29143935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saal an der Donau subcamp |
E738715
|
entity |
| Predicate | subjectedPrisonersTo |
P83128
|
FINISHED |
| Object | inhumane 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: inhumane conditions | Statement: [Saal an der Donau subcamp, subjectedPrisonersTo, inhumane conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectedPrisonersTo Context triple: [Saal an der Donau subcamp, subjectedPrisonersTo, inhumane conditions]
-
A.
useOfTorture
Indicates the intentional infliction or use of torture by one entity upon another, typically to punish, coerce, intimidate, or extract information.
-
B.
effectOnPrisoners
chosen
Indicates the impact or consequences that something has on prisoners.
-
C.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
D.
numberOfTortureVictims
Indicates the quantity of individuals who have been subjected to torture.
-
E.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 11:38 a.m.