Triple
T5056584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Internal Affairs of the USSR |
E113917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state security body |
C3363
|
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: state security body Context triple: [Ministry of Internal Affairs of the USSR, instanceOf, state security body]
-
A.
state security agency
chosen
A state security agency is a government organization responsible for protecting national security through intelligence gathering, counterintelligence, and enforcement activities aimed at preventing internal and external threats.
-
B.
security agency
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
C.
domestic intelligence agency
A domestic intelligence agency is a government organization responsible for collecting, analyzing, and acting on information related to internal security threats within a country's borders, such as terrorism, espionage, and subversion.
-
D.
national security system
A national security system is an integrated framework of institutions, policies, technologies, and processes designed to protect a nation’s sovereignty, citizens, critical infrastructure, and interests from internal and external threats.
-
E.
secret government agency
A secret government agency is a covert, officially sanctioned organization that operates outside public scrutiny to conduct sensitive intelligence, security, or special operations in the interest of national or global objectives.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:38 p.m.