Triple
T31256058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitry Kovtun |
E796973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former KGB officer |
C35117
|
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: former KGB officer Context triple: [Dmitry Kovtun, instanceOf, former KGB officer]
-
A.
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.
-
B.
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.
-
C.
former intelligence operative
chosen
A former intelligence operative is an individual who previously worked in covert information-gathering, analysis, or clandestine operations for a government or private intelligence organization and has since left active service.
-
D.
former CIA officer
A former CIA officer is an individual who previously served in the Central Intelligence Agency, typically involved in intelligence collection, analysis, or covert operations, but is no longer actively employed by the agency.
-
E.
KGB chairman
The KGB chairman is the highest-ranking official overseeing the Soviet Union’s state security and intelligence agency, responsible for directing espionage, counterintelligence, internal security, and political repression operations.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:12 p.m.