Triple
T34683009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicherheitsapparat der DDR |
E890668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | staatlicher Sicherheitsapparat |
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: staatlicher Sicherheitsapparat Context triple: [Sicherheitsapparat der DDR, instanceOf, staatlicher Sicherheitsapparat]
-
A.
public security organ
A public security organ is a government agency responsible for maintaining public order, preventing and investigating crimes, and safeguarding the security and stability of society.
-
B.
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.
-
C.
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.
-
D.
политическая полиция
Политическая полиция — это специализированный государственный орган, занимающийся наблюдением, контролем и преследованием политической оппозиции и инакомыслия с целью сохранения существующего политического строя.
-
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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.