Triple
T38604776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black operations |
E934312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence operation type |
C35775
|
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 operation type Context triple: [black operations, instanceOf, intelligence operation type]
-
A.
covert intelligence operation
chosen
A covert intelligence operation is a secretive, state-directed activity designed to gather information or influence events without revealing the sponsor’s identity or involvement.
-
B.
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.
-
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.
signals intelligence program
A signals intelligence program is a coordinated set of activities, technologies, and procedures designed to collect, process, analyze, and exploit electronic signals and communications for intelligence and security purposes.
-
E.
intelligence directive
An intelligence directive is a formal instruction or guiding framework that defines the objectives, priorities, and constraints for the collection, analysis, and dissemination of intelligence information.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.