Triple
T32256967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pléiades Neo |
E824051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial satellite constellation |
C26932
|
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: commercial satellite constellation Context triple: [Pléiades Neo, instanceOf, commercial satellite constellation]
-
A.
remote sensing satellite constellation
chosen
A remote sensing satellite constellation is a coordinated network of satellites designed to collect and transmit Earth observation data—such as imagery, environmental measurements, and geospatial information—at high temporal and spatial resolution.
-
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.
high-throughput satellite
A high-throughput satellite is a communications satellite that uses advanced frequency reuse and spot-beam technologies to deliver significantly higher data capacity and throughput than traditional satellites over the same spectrum.
-
D.
military satellite
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.
-
E.
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.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.