Triple
T2178559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Internal Troops |
E48587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal security force |
C6385
|
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: internal security force Context triple: [Soviet Internal Troops, instanceOf, internal security force]
-
A.
security force
chosen
A security force is an organized group responsible for protecting people, property, and interests by preventing, detecting, and responding to threats or unlawful activities.
-
B.
interior ministry
The interior ministry is a government department responsible for domestic affairs, including internal security, public administration, civil registration, and often oversight of police and emergency services.
-
C.
police force
A police force is an organized body of officers empowered by a government to maintain public order, enforce laws, prevent and investigate crime, and protect citizens and property.
-
D.
state security agency
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.
-
E.
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.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.