Triple
T16920775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinel-6 |
E410437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ocean altimetry satellite |
C28991
|
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: ocean altimetry satellite Context triple: [Sentinel-6, instanceOf, ocean altimetry satellite]
-
A.
remote sensing satellite
chosen
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.
-
B.
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.
-
C.
ocean observing program
An ocean observing program is a coordinated, long-term effort that systematically measures and monitors physical, chemical, biological, and geological properties of the ocean to support research, forecasting, and resource management.
-
D.
autonomous oceanographic instrument
An autonomous oceanographic instrument is a self-contained, untethered device designed to operate independently in marine environments, collecting and transmitting physical, chemical, or biological ocean data over extended periods without direct human intervention.
-
E.
geostationary weather satellite
A geostationary weather satellite is an Earth-orbiting spacecraft positioned over the equator at a fixed longitude, continuously monitoring the same region to collect atmospheric and surface data for weather observation and forecasting.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.