Triple
T3685007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauleiter of Franconia |
E78202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi Party political office |
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: Nazi Party political office Context triple: [Gauleiter of Franconia, instanceOf, Nazi Party political office]
-
A.
member of the National Socialist German Workers' Party
A member of the National Socialist German Workers' Party is an individual who formally belonged to and supported the Nazi political organization that ruled Germany under Adolf Hitler from 1933 to 1945.
-
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.
organ of the National Fascist Party
An organ of the National Fascist Party is an official body, institution, or publication that operates under the party’s authority to implement, communicate, or enforce its policies and ideology.
-
D.
Ba'ath Party official
A Ba'ath Party official is a political functionary or leader who holds an appointed or elected position within the organizational hierarchy of the Ba'ath Party, responsible for implementing its Arab nationalist and socialist policies.
-
E.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.