Triple
T23643016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henning von Tresckow |
E583951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conspirator in the 20 July plot |
C26947
|
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: conspirator in the 20 July plot Context triple: [Henning von Tresckow, instanceOf, conspirator in the 20 July plot]
-
A.
Nazi Germany dissident
chosen
A Nazi Germany dissident is an individual who actively opposed, resisted, or subverted the policies, ideology, or authority of the Nazi regime within Germany between 1933 and 1945.
-
B.
member of Nazi inner circle
A member of the Nazi inner circle is a high-ranking, influential individual who directly participated in shaping, directing, and sustaining the core leadership, policies, and operations of the National Socialist regime.
-
C.
member of Narodnaya Volya
A member of Narodnaya Volya is an individual who belonged to the 19th-century Russian revolutionary organization dedicated to overthrowing the tsarist autocracy through political terrorism and clandestine activism.
-
D.
member of the Committee of Public Safety
A member of the Committee of Public Safety is an appointed revolutionary official in late 18th-century France responsible for directing war efforts, internal security, and political oversight during the Reign of Terror.
-
E.
Nazi official
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.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:48 p.m.