Triple
T33987595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western intelligence services |
E871454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence agency collective |
C1662
|
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: intelligence agency collective Context triple: [Western intelligence services, instanceOf, intelligence agency collective]
-
A.
intelligence agency system
An intelligence agency system is an integrated framework of tools, processes, and organizational structures that collects, analyzes, secures, and disseminates sensitive information to support national security and strategic decision-making.
-
B.
intelligence analysis agency
An intelligence analysis agency is an organization that collects, evaluates, and interprets information from various sources to produce assessments that support decision-making, security, and policy formulation.
-
C.
intelligence community
chosen
The intelligence community is a collective network of government agencies and organizations responsible for gathering, analyzing, and disseminating information to support national security and foreign policy decision-making.
-
D.
espionage agency
An espionage agency is a covert government or private organization responsible for gathering, analyzing, and acting on secret information to protect or advance national or organizational interests.
-
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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.