Triple

T3742222
Position Surface form Disambiguated ID Type / Status
Subject SS-Brigadeführer E79727 entity
Predicate higherRank P301 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: [SS-Brigadeführer, higherRank, SS-Gruppenführer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SS-Gruppenführer
Context triple: [SS-Brigadeführer, higherRank, 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_69ad8b115610819095b02007da5ca3cb completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb563fac8190b6a55580d0386e8a completed March 8, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4fb0c116c8190a74fff15a5de8296 completed March 14, 2026, 6:07 a.m.
Created at: March 8, 2026, 3:34 p.m.