Triple
T15746385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Departments |
E381731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet security agency unit |
C16774
|
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 agency unit Context triple: [Special Departments, instanceOf, Soviet security agency unit]
-
A.
Office of Strategic Services unit
An Office of Strategic Services unit is a specialized World War II-era U.S. intelligence and covert operations group responsible for espionage, sabotage, and support to resistance movements behind enemy lines.
-
B.
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.
-
C.
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.
-
D.
directorate of the Ministry of Defense of the USSR
A directorate of the Ministry of Defense of the USSR was a specialized administrative and command body responsible for managing a specific functional area of military policy, operations, or support within the Soviet armed forces.
-
E.
Soviet organization
chosen
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.