Triple
T11736233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semyon Ignatyev |
E279032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet state security official |
C16834
|
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: Soviet state security official Context triple: [Semyon Ignatyev, instanceOf, Soviet state security official]
-
A.
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.
-
B.
NKVD officer
chosen
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.
-
C.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
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.
period of the Soviet security services
The period of the Soviet security services encompasses the historical evolution, organizational structures, operational practices, and political roles of Soviet state security organs from the Bolshevik Revolution through the dissolution of the USSR.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.