Triple
T19753086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSP-16 |
E474431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Defense Support Program 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: Defense Support Program satellite Context triple: [DSP-16, instanceOf, Defense Support Program 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.
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.
-
C.
satellite system
A satellite system is an integrated network of orbiting spacecraft, ground stations, and communication links designed to perform functions such as communication, navigation, Earth observation, or scientific research.
-
D.
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.
-
E.
polar-orbiting satellite
A polar-orbiting satellite is a spacecraft that travels in a low Earth orbit passing close to the poles, allowing it to observe the entire Earth's surface over time as the planet rotates beneath it.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.