Triple
T36914101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 175th Cyberspace Operations Group |
E912997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyberspace operations group |
C41697
|
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: cyberspace operations group Context triple: [175th Cyberspace Operations Group, instanceOf, cyberspace operations group]
-
A.
cyberspace operations command
A cyberspace operations command is a military or governmental organizational entity responsible for planning, directing, and executing offensive, defensive, and support activities within and through cyberspace to achieve strategic and operational objectives.
-
B.
cyberspace operations component
chosen
A cyberspace operations component is an organizational element responsible for planning, directing, and executing military or security activities within and through cyberspace to achieve assigned objectives.
-
C.
cybersecurity coordination body
A cybersecurity coordination body is an organization that facilitates collaboration, information sharing, and joint response among stakeholders to prevent, detect, and mitigate cyber threats.
-
D.
electronic warfare command
An electronic warfare command is an organizational unit responsible for planning, coordinating, and executing operations that use the electromagnetic spectrum to detect, disrupt, deceive, or protect against adversary electronic systems.
-
E.
military operations center
A military operations center is a centralized facility where commanders and staff monitor, coordinate, and direct military activities and resources in real time.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.