Triple
T22958333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSO |
E570821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military Earth observation satellite system |
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: military Earth observation satellite system Context triple: [CSO, instanceOf, military Earth observation satellite system]
-
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 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.
-
C.
remote sensing satellite
A remote sensing satellite is an orbiting spacecraft equipped with sensors that collect data about the Earth's surface and atmosphere for applications such as mapping, environmental monitoring, and resource management.
-
D.
satellite-based Earth observation service
A satellite-based Earth observation service collects, processes, and delivers remotely sensed data about the Earth's surface and atmosphere to support applications such as environmental monitoring, resource management, and disaster response.
-
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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:47 p.m.