Triple
T36514566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAPPHIRE |
E900001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space surveillance satellite |
C37940
|
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 surveillance satellite Context triple: [SAPPHIRE, instanceOf, space surveillance satellite]
-
A.
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.
-
B.
military satellite
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.
-
C.
space weather monitoring satellite
A space weather monitoring satellite is an orbiting spacecraft equipped with instruments to observe and measure solar activity and its effects on the near-Earth space environment for forecasting and research.
-
D.
satellite surveillance base
A satellite surveillance base is a secure ground facility equipped with advanced antennas, control systems, and data-processing infrastructure used to monitor, receive, analyze, and manage information from surveillance satellites orbiting the Earth.
-
E.
Earth-orbiting satellite
chosen
An Earth-orbiting satellite is a human-made object placed into a stable or semi-stable trajectory around Earth to perform functions such as communication, navigation, observation, 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.