Triple
T17712404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Space Force intelligence enterprise |
E441602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space intelligence enterprise |
C24952
|
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: space intelligence enterprise Context triple: [United States Space Force intelligence enterprise, instanceOf, space intelligence enterprise]
-
A.
intelligence, surveillance, and reconnaissance enterprise
chosen
An intelligence, surveillance, and reconnaissance enterprise is an integrated system of people, processes, and technologies that collects, analyzes, and disseminates information to provide timely situational awareness and decision support.
-
B.
space domain awareness unit
A space domain awareness unit is an organizational entity responsible for detecting, tracking, characterizing, and assessing objects and activities in space to support space operations and security.
-
C.
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.
-
D.
geospatial intelligence facility
A geospatial intelligence facility is a secure, specialized site where experts collect, process, analyze, and disseminate geographic and imagery data to support military, intelligence, and strategic decision-making.
-
E.
space surveillance sensor
A space surveillance sensor is a device or system that detects, tracks, and characterizes objects in space to support situational awareness, collision avoidance, and space traffic management.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:06 a.m.