Triple
T19210939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JFHQ–DODIN |
E480354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyberspace operations command |
C41698
|
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 command Context triple: [JFHQ–DODIN, instanceOf, cyberspace operations command]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Air and Space Operations Center
An Air and Space Operations Center is a command and control facility that plans, directs, coordinates, and monitors air and space operations to achieve assigned military objectives.
- F. None of above. chosen
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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:21 p.m.