Triple
T4929714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Forces Cyber |
E110664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber command |
C298
|
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: military cyber command Context triple: [Air Forces Cyber, instanceOf, military cyber command]
-
A.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
B.
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.
-
C.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
United States Space Force field command
A United States Space Force field command is a major organizational echelon responsible for executing a broad, mission-specific portfolio of space operations, support, or training functions under the direction of Space Operations Command.
-
E.
maritime command and control framework
A maritime command and control framework is an integrated structure of processes, technologies, and organizational roles that enables coordinated planning, decision-making, and execution of naval and maritime operations across multiple domains and stakeholders.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:30 p.m.