Triple
T12271668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFSCC |
E292484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combined space operations command |
C8007
|
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: combined space operations command Context triple: [CFSCC, instanceOf, combined space 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.
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.
-
C.
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.
-
D.
mission commander
A mission commander is the individual responsible for planning, directing, and overseeing the successful execution and safety of an entire mission and its team.
-
E.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.