Triple
T18574383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUSCULAR |
E453948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | signals intelligence operation |
C13392
|
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: signals intelligence operation Context triple: [MUSCULAR, instanceOf, signals intelligence operation]
-
A.
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.
-
B.
signals intelligence alliance
A signals intelligence alliance is a cooperative partnership between nations or organizations to collect, share, and analyze electronic communications and signals data for security, defense, and strategic purposes.
-
C.
signals intelligence program
chosen
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.
-
D.
signals intelligence system
A signals intelligence system is an integrated set of tools, sensors, and processes designed to intercept, collect, analyze, and exploit electronic signals and communications for intelligence and security purposes.
-
E.
signals intelligence facility
A signals intelligence facility is a secure installation equipped with specialized systems and personnel dedicated to intercepting, processing, analyzing, and disseminating electronic communications and emissions for intelligence and security purposes.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.