Triple
T16378000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amt für Nationale Sicherheit |
E397726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government security agency |
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: government security agency Context triple: [Amt für Nationale Sicherheit, instanceOf, government security agency]
-
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.
security agency
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
C.
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.
-
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.
intelligence agency division
A specialized organizational unit within an intelligence agency responsible for focused functions such as collection, analysis, operations, or support in pursuit of national security 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.