Triple
T702957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NKVD |
E14038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet state security agency |
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: Soviet state security agency Context triple: [NKVD, instanceOf, Soviet state security agency]
-
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.
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.
-
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.
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.
CIA directorate
A CIA directorate is a major organizational division within the Central Intelligence Agency responsible for a specific core function such as intelligence analysis, clandestine operations, science and technology, or support services.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.