Triple
T6249018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Nebe |
E139996
|
entity |
| Predicate | militaryRank |
P342
|
FINISHED |
| Object | SS-Gruppenführer |
E209682
|
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: SS-Gruppenführer | Statement: [Arthur Nebe, militaryRank, SS-Gruppenführer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SS-Gruppenführer Context triple: [Arthur Nebe, militaryRank, SS-Gruppenführer]
-
A.
SS-Gruppenführer
chosen
SS-Gruppenführer was a high-ranking paramilitary rank in the Schutzstaffel (SS) of Nazi Germany, roughly equivalent to a lieutenant general.
-
B.
SS-Scharführer
SS-Scharführer was a non-commissioned officer rank in the Schutzstaffel (SS) of Nazi Germany, roughly equivalent to a sergeant.
-
C.
SS-Standartenführer
SS-Standartenführer was a senior commissioned officer rank in the Nazi Schutzstaffel (SS), roughly equivalent to a colonel in traditional military hierarchies.
-
D.
SS-Sturmbannführer
SS-Sturmbannführer was a mid-level paramilitary rank in the Nazi Schutzstaffel (SS), roughly equivalent to a major in the army.
-
E.
SS-Brigadeführer
SS-Brigadeführer was a senior paramilitary rank in the Nazi Schutzstaffel (SS), roughly equivalent to a brigadier general in the army.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633c5f2081909b0246e061f8a7d9 |
completed | March 22, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5191d2d248190b34edca246ee74b8 |
completed | March 26, 2026, 11:31 a.m. |
Created at: March 22, 2026, 4:24 p.m.