Triple
T16487785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationaler Verteidigungsrat der DDR |
E400491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sicherheitsorgan |
C3365
|
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: Sicherheitsorgan Context triple: [Nationaler Verteidigungsrat der DDR, instanceOf, Sicherheitsorgan]
-
A.
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.
-
B.
карательный орган
Карательный орган — это государственная или окологосударственная структура, наделённая полномочиями применять репрессивные меры, включая наказания и принуждение, для подавления нарушений установленных норм и поддержания существующего порядка.
-
C.
security agency
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
D.
domestic intelligence agency
chosen
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.
-
E.
parliamentary security organization
A parliamentary security organization is a specialized body responsible for protecting the legislature’s members, staff, visitors, facilities, and information while supporting the safe and orderly conduct of parliamentary business.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:13 a.m.