Triple
T12271667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFSCC |
E292484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military space command component |
C2647
|
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 space command component Context triple: [CFSCC, instanceOf, military space command component]
-
A.
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.
-
B.
space operations command
chosen
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.
-
C.
United States Space Force organizational system
The United States Space Force organizational system is the structured arrangement of commands, field units, roles, and processes designed to plan, conduct, and support space operations in alignment with national defense objectives.
-
D.
U.S. Space Force mission area
A U.S. Space Force mission area is a defined domain of responsibility that encompasses specific space-related operations, capabilities, and objectives required to support national security and joint military missions.
-
E.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
- 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.