Triple
T23312823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STIX |
E590627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyber threat intelligence language |
C35432
|
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: cyber threat intelligence language Context triple: [STIX, instanceOf, cyber threat intelligence language]
-
A.
signals intelligence tool
A signals intelligence tool is a system that intercepts, processes, and analyzes electronic signals and communications to extract actionable information and insights.
-
B.
security intelligence platform
chosen
A security intelligence platform is an integrated system that collects, correlates, and analyzes security-related data from diverse sources to provide actionable insights for detecting, investigating, and responding to threats.
-
C.
intelligence assessment
An intelligence assessment is a systematic evaluation process used to measure, analyze, and interpret an individual’s or group’s cognitive abilities, problem-solving skills, and related mental capacities for decision-making or diagnostic purposes.
-
D.
intelligence analysis course
An intelligence analysis course teaches students systematic methods, tools, and critical thinking skills to collect, evaluate, and interpret information for informed decision-making in security, policy, or organizational contexts.
-
E.
terrorism threat advisory system
A terrorism threat advisory system is a structured framework that continuously assesses, categorizes, and communicates the likelihood and severity of terrorist activities to guide security measures and public awareness.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.