Triple
T36486029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Space Surveillance System |
E898934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space situational awareness network |
C15703
|
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 situational awareness network Context triple: [Canadian Space Surveillance System, instanceOf, space situational awareness network]
-
A.
space domain awareness unit
chosen
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.
-
B.
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.
-
C.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
D.
space operations center
A space operations center is a specialized facility that monitors, controls, and coordinates spacecraft, satellites, and related space missions in real time.
-
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.