Triple
T3577514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Council Intelligence Directive 9 |
E75723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence directive |
C13390
|
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 directive Context triple: [National Security Council Intelligence Directive 9, instanceOf, intelligence directive]
-
A.
intelligence budget
An intelligence budget is the planned allocation of financial and resource expenditures dedicated to gathering, analyzing, and applying information to support decision-making and strategic objectives.
-
B.
intelligence officer
An intelligence officer is a professional responsible for collecting, analyzing, and disseminating sensitive information to support national security, military operations, or organizational decision-making.
-
C.
signals intelligence agency
A signals intelligence agency is an organization responsible for intercepting, analyzing, and exploiting electronic communications and signals to support national security, defense, and law enforcement objectives.
-
D.
intelligence research agency
An intelligence research agency is an organization dedicated to systematically collecting, analyzing, and interpreting information to produce actionable insights for strategic, security, or policy decision-making.
-
E.
intelligence organization unit
An intelligence organization unit is a structured group within an intelligence agency responsible for collecting, analyzing, and disseminating information to support decision-making and security objectives.
- F. None of above. chosen
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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:21 p.m.