Triple
T4715288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franz Reichleitner |
E104621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austrian SS officer |
C2513
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Austrian SS officer Context triple: [Franz Reichleitner, instanceOf, Austrian SS officer]
-
A.
Waffen-SS officer
A Waffen-SS officer was a commissioned leader within Nazi Germany’s Waffen-SS, responsible for commanding combat units of this paramilitary organization that was deeply involved in war crimes and atrocities during World War II.
-
B.
Nazi official
chosen
A Nazi official is a person who held an administrative, political, or military position within the National Socialist (Nazi) regime in Germany, responsible for implementing and enforcing its totalitarian, racist, and genocidal policies.
-
C.
Austrian general
An Austrian general is a high-ranking military officer from Austria responsible for planning, directing, and overseeing large-scale military operations and strategic defense initiatives.
-
D.
Waffen-SS corps
The Waffen-SS corps was the combat branch of Nazi Germany’s SS organization, comprising ideologically driven, militarized units that fought alongside the regular army and were heavily involved in war crimes and atrocities during World War II.
-
E.
Bavarian civil servant
A Bavarian civil servant is a public-sector employee working within the administrative, legal, or regulatory institutions of the Free State of Bavaria, responsible for implementing laws, delivering public services, and upholding regional and federal regulations.
- F. None of above.
Provenance (1 batch)
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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:18 p.m.