Triple
T75637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SovietPrisonersOfWar |
E1511
|
entity |
| Predicate | legalStatusInNaziView |
P4716
|
FINISHED |
| Object | subhuman |
—
|
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: subhuman | Statement: [SovietPrisonersOfWar, legalStatusInNaziView, subhuman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInNaziView Context triple: [SovietPrisonersOfWar, legalStatusInNaziView, subhuman]
-
A.
LiberationOfAuschwitz
Indicates the act or event of freeing prisoners and ending Nazi control at the Auschwitz concentration camp.
-
B.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
C.
estimatedNumberOfSurvivorsAtLiberation
Indicates the approximate count of individuals who were still alive at the time a camp or similar site was liberated.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
numberOfPeopleExecuted
Indicates the total count of individuals who were put to death, typically as a result of a formal execution process.
- F. None of above. chosen
Provenance (4 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a25313f1688190ba0fa8677faaf65b |
completed | Feb. 28, 2026, 2:29 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.