Triple
T36223858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxar 1300-class bus |
E1047928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geostationary satellite platform |
C42677
|
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 platform Context triple: [Maxar 1300-class bus, instanceOf, geostationary satellite platform]
-
A.
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.
-
B.
satellite platform derivative
chosen
A satellite platform derivative is a modified version of an existing satellite bus or platform, adapted with changes in structure, subsystems, or payload interfaces to meet new mission requirements while leveraging the original design.
-
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.
geostationary orbit
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.
-
E.
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.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.