Triple
T33000443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMERSH |
E844350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military counterintelligence organization |
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 military counterintelligence organization Context triple: [SMERSH, instanceOf, Soviet military counterintelligence organization]
-
A.
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.
-
B.
KGB division
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.
-
C.
British intelligence agency
A British intelligence agency is a government organization responsible for gathering, analyzing, and acting on information to protect the United Kingdom’s national security and interests at home and abroad.
-
D.
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.
-
E.
East German security force branch
A specialized organizational unit within the security apparatus of the former East Germany (GDR), responsible for specific protective, intelligence, policing, or border-control functions under state authority.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.