Triple
T28711503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ball Configurable Platform |
E729842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite bus architecture |
C45109
|
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: satellite bus architecture Context triple: [Ball Configurable Platform, instanceOf, satellite bus architecture]
-
A.
satellite platform derivative
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.
-
B.
spacecraft onboard computer
A spacecraft onboard computer is a specialized, radiation-hardened computing system that autonomously manages spacecraft functions, navigation, communication, and data handling in the harsh environment of space.
-
C.
spacecraft payload platform
chosen
A spacecraft payload platform is the structural and functional subsystem that supports, powers, interfaces, and stabilizes scientific instruments or mission-specific equipment aboard a spacecraft.
-
D.
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.
-
E.
satellite navigation infrastructure component
A satellite navigation infrastructure component is a physical or logical element—such as satellites, ground stations, control systems, or communication links—that collectively enables the generation, transmission, correction, and reception of positioning, navigation, and timing signals.
- 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.