Triple
T33168727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyotr Rachkovsky |
E848967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian secret police official |
C60518
|
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: Russian secret police official Context triple: [Pyotr Rachkovsky, instanceOf, Russian secret police official]
-
A.
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.
-
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.
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.
-
D.
CIA official
A CIA official is a government intelligence professional responsible for overseeing, coordinating, or executing activities related to the collection, analysis, and protection of sensitive national security information.
-
E.
Cuban intelligence officer
A Cuban intelligence officer is a government agent responsible for gathering, analyzing, and protecting sensitive information to support Cuba’s national security and strategic interests, often through covert operations and counterintelligence activities.
- F. None of above. chosen
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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.