Triple
T23250696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astra 19.2°E |
E581723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geostationary satellite orbital position |
C41656
|
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: geostationary satellite orbital position Context triple: [Astra 19.2°E, instanceOf, geostationary satellite orbital position]
-
A.
geostationary orbit
chosen
A geostationary orbit is a circular, equatorial orbit around Earth in which a satellite moves at the same rotational speed as the planet, appearing fixed over a single point on the equator.
-
B.
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.
-
C.
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.
-
D.
heliosynchronous orbit
A heliosynchronous orbit is a near-polar, Sun-synchronous Earth orbit in which a satellite passes over any given point on the planet at the same local solar time, maintaining consistent lighting conditions for imaging and observation.
-
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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:10 p.m.