Triple
T33573071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Grubitz |
E859954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stasi officer |
C48314
|
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: Stasi officer Context triple: [Anton Grubitz, instanceOf, Stasi officer]
-
A.
Stasi official
chosen
A Stasi official is a government functionary of East Germany’s Ministry for State Security responsible for overseeing surveillance, intelligence gathering, and political repression to maintain state control.
-
B.
Cheka officer
A Cheka officer is a member of the early Soviet secret police responsible for internal security, political repression, and the suppression of perceived enemies of the Bolshevik regime.
-
C.
NKVD officer
An NKVD officer is a member of the Soviet Union’s internal security and secret police organization responsible for intelligence, political repression, and enforcement of state control during the Stalinist era.
-
D.
Russian secret police official
A Russian secret police official is a government security officer responsible for intelligence gathering, political surveillance, and the suppression of perceived internal and external threats to the state.
-
E.
Soviet agent
A Soviet agent is an individual who covertly gathers, transmits, or influences information and activities on behalf of the Soviet state’s intelligence or security services, often operating under false identities or clandestine arrangements.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.