Triple
T1706175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Államvédelmi Hatóság |
E36876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secret police organization |
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: secret police organization Context triple: [Államvédelmi Hatóság, instanceOf, secret police organization]
-
A.
clandestine group
A clandestine group is a secretive organization whose members covertly coordinate activities, often to pursue hidden political, criminal, or subversive objectives while avoiding detection by authorities or the public.
-
B.
covert intelligence organization
A covert intelligence organization is a secretive entity that gathers, analyzes, and acts on sensitive information through clandestine methods to influence or protect national or organizational interests.
-
C.
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.
-
D.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.