Triple
T10141333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Abakumov |
E231590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet 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 security official Context triple: [Viktor Abakumov, instanceOf, Soviet 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.
Russian diplomat
A Russian diplomat is an official representative of the Russian Federation who conducts negotiations, manages international relations, and protects Russia’s interests and citizens abroad through diplomatic channels.
-
E.
Soviet Air Defense Forces commander
A Soviet Air Defense Forces commander was a high-ranking military officer responsible for planning, directing, and coordinating the detection, interception, and destruction of hostile aerial threats within the airspace of the Soviet Union and its allies.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.