Triple
T5271731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | police forces of St. Petersburg |
E119273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tsarist security apparatus |
C860
|
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: Tsarist security apparatus Context triple: [police forces of St. Petersburg, instanceOf, Tsarist security apparatus]
-
A.
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.
-
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.
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.
instrument of state terror
chosen
An instrument of state terror is any tool, policy, institution, or practice deliberately used by a government to instill fear, suppress dissent, and maintain control through intimidation and violence.
-
E.
Pinkerton detective
A Pinkerton detective is a private investigator employed by the Pinkerton National Detective Agency, historically known for security work, strikebreaking, and pursuing high-profile criminals in the United States.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:51 p.m.