Triple
T4603690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross-Mission Ground and Communications |
E100378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Space Systems Command enterprise |
C6111
|
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: U.S. Space Systems Command enterprise Context triple: [Cross-Mission Ground and Communications, instanceOf, U.S. Space Systems Command enterprise]
-
A.
United States Space Force field command
chosen
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
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.
NASA division
A NASA division is an organizational unit within NASA responsible for managing specific programs, research areas, or operational functions to support the agency’s overall space and aeronautics mission.
-
D.
United States Navy systems command
The United States Navy systems command is an organizational entity responsible for developing, acquiring, and sustaining specific categories of naval systems, equipment, and technologies in support of fleet operations.
-
E.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.