Triple
T8372398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rasse- und Siedlungshauptamt der SS |
E197489
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | RuSHA |
E197490
|
NE 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: RuSHA | Statement: [Rasse- und Siedlungshauptamt der SS, shortName, RuSHA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RuSHA Context triple: [Rasse- und Siedlungshauptamt der SS, shortName, RuSHA]
-
A.
RuSHA
chosen
RuSHA was a Nazi SS office responsible for implementing racial policies, including racial selection, resettlement, and the persecution and displacement of populations in occupied territories.
-
B.
Resh
Resh is the twentieth letter of the Hebrew alphabet, representing an "r" sound and used in both Hebrew writing and numerology.
-
C.
RSH
RSH is the National Rail station code for Ramsgreave and Wilpshire railway station in Lancashire, England.
-
D.
RuSHA Trial
The RuSHA Trial was one of the Subsequent Nuremberg Trials in which SS officials were prosecuted for implementing Nazi racial policies, including forced resettlement, kidnapping of children, and persecution based on racial criteria.
-
E.
Rsh
Rsh is a protocol used within the Hydra ecosystem, likely related to its communication or operational framework.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a6944081909c4547688c9e70ae |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce02aab4488190abc63bace296e32a |
completed | April 2, 2026, 5:46 a.m. |
Created at: March 30, 2026, 6:01 p.m.