Triple
T9413632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBAS-2 |
E226761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Space Force satellite |
C25837
|
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 Force satellite Context triple: [CBAS-2, instanceOf, U.S. Space Force satellite]
-
A.
military satellite
chosen
A military satellite is an artificial satellite deployed and operated by armed forces to support defense-related functions such as reconnaissance, communications, navigation, early warning, and targeting.
-
B.
United States Space Force delta
A United States Space Force delta is a military organizational unit, roughly equivalent to a wing, that is responsible for a specific mission area such as operations, training, or support within the Space Force.
-
C.
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.
-
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.
satellite program
A satellite program is an organized initiative that designs, builds, launches, and operates satellites to achieve specific objectives such as communication, Earth observation, navigation, or scientific research.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:47 p.m.