Triple

T6511529
Position Surface form Disambiguated ID Type / Status
Subject Joachim Peiper E150145 entity
Predicate SSRank P22188 FINISHED
Object SS-Standartenführer E81644 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-Standartenführer | Statement: [Joachim Peiper, SSRank, SS-Standartenführer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SS-Standartenführer
Context triple: [Joachim Peiper, SSRank, SS-Standartenführer]
  • A. SS-Standartenführer chosen
    SS-Standartenführer was a senior commissioned officer rank in the Nazi Schutzstaffel (SS), roughly equivalent to a colonel in traditional military hierarchies.
  • B. 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.
  • C. SS-Scharführer
    SS-Scharführer was a non-commissioned officer rank in the Schutzstaffel (SS) of Nazi Germany, roughly equivalent to a sergeant.
  • D. SS-Gruppenführer
    SS-Gruppenführer was a high-ranking paramilitary rank in the Schutzstaffel (SS) of Nazi Germany, roughly equivalent to a lieutenant general.
  • E. SS-Obersturmbannführer
    SS-Obersturmbannführer was a mid- to senior-level paramilitary rank in the Nazi Schutzstaffel (SS), roughly equivalent to a lieutenant colonel.
  • 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_69c687ef291081909d437f035eef1cda completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69f3ad7d081909162f1a625fc52b1 completed March 27, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cb6421748190b8f2b77c77b153bc completed March 27, 2026, 6:24 p.m.
Created at: March 27, 2026, 1:43 p.m.