Triple
T27539995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APPF |
E695208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-owned security 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: state-owned security organization Context triple: [APPF, instanceOf, state-owned security organization]
-
A.
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.
-
B.
government-backed organization
A government-backed organization is an entity that operates with financial support, authorization, or guarantees from a government to carry out specific public, economic, or policy-related functions.
-
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.
national security authority
A national security authority is a governmental body responsible for safeguarding a nation’s security interests by overseeing intelligence, defense coordination, threat assessment, and the protection of critical assets and information.
-
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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:30 p.m.