Triple
T2002791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber Command (Belgium) |
E43508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyber command |
C409
|
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 command Context triple: [Cyber Command (Belgium), instanceOf, cyber command]
-
A.
cybersecurity agency
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
B.
component of the Cybersecurity and Infrastructure Security Agency
A component of the Cybersecurity and Infrastructure Security Agency is an organizational unit or program within CISA that carries out specific cybersecurity, infrastructure protection, emergency communications, or risk management functions in support of the agency’s mission.
-
C.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
-
D.
joint command
chosen
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
E.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.