Triple
T28711355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metop satellites |
E729839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | polar-orbiting satellites |
C23970
|
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: polar-orbiting satellites Context triple: [Metop satellites, instanceOf, polar-orbiting satellites]
-
A.
polar-orbiting satellite
chosen
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.
-
B.
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.
-
C.
Earth-orbiting satellite
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.
-
D.
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.
-
E.
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.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:48 a.m.