Triple
T32822324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department A |
E839466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | KGB department |
C58002
|
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: KGB department Context triple: [Department A, instanceOf, KGB department]
-
A.
KGB division
chosen
A KGB division is an organizational unit within the Soviet Union’s state security agency responsible for specialized functions such as intelligence, counterintelligence, surveillance, or internal security operations.
-
B.
department of the Communist Party of the Soviet Union
A department of the Communist Party of the Soviet Union was an organizational unit within the Party’s central or regional apparatus responsible for directing, coordinating, and supervising specific policy areas, sectors, or administrative functions across the state and society.
-
C.
политическая полиция
Политическая полиция — это специализированный государственный орган, занимающийся наблюдением, контролем и преследованием политической оппозиции и инакомыслия с целью сохранения существующего политического строя.
-
D.
Soviet government ministry
A Soviet government ministry was a centralized state administrative body responsible for directing and managing a specific sector of the economy, society, or state functions under the authority of the USSR’s Communist Party leadership.
-
E.
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.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:15 a.m.