Triple
T3492761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Support Program |
E73775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early-warning satellite system |
C9200
|
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: early-warning satellite system Context triple: [Defense Support Program, instanceOf, early-warning satellite system]
-
A.
polar-orbiting weather satellite program
A polar-orbiting weather satellite program is a coordinated system of satellites in near-polar orbits that provide global, high-resolution observations of atmospheric, oceanic, and surface conditions for weather forecasting and climate monitoring.
-
B.
public warning system
A public warning system is an organized infrastructure of technologies, protocols, and communication channels designed to rapidly alert and inform the public about imminent or ongoing emergencies and hazards.
-
C.
satellite program
chosen
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.
-
D.
Global Navigation Satellite System
A Global Navigation Satellite System is a satellite-based infrastructure that provides continuous, worldwide positioning, navigation, and timing services to receivers on or near Earth’s surface.
-
E.
geostationary communications satellite
A geostationary communications satellite is a spacecraft positioned in an equatorial orbit that matches Earth's rotation, remaining fixed over one longitude to relay telecommunications signals between ground stations.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.