Triple
T28711262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Search and Rescue Satellite-Aided Tracking payload |
E729837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite payload |
C55198
|
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 payload Context triple: [Search and Rescue Satellite-Aided Tracking payload, instanceOf, satellite payload]
-
A.
spacecraft payload platform
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.
-
B.
communications payload
A communications payload is the collection of onboard equipment and subsystems on a spacecraft or platform dedicated to receiving, processing, and transmitting communication signals between space and ground or between nodes in a network.
-
C.
NASA payload
A NASA payload is the collection of scientific instruments, technology demonstrations, or mission-specific equipment carried by a spacecraft or launch vehicle to achieve its research and exploration objectives.
-
D.
secondary payload
A secondary payload is an additional, typically smaller or lower-priority cargo or instrument carried alongside a primary payload on a mission or transport system, sharing available capacity and resources.
-
E.
scientific payload
A scientific payload is the collection of instruments, sensors, and supporting equipment carried by a vehicle (such as a satellite, rocket, or aircraft) specifically to conduct experiments and gather scientific data.
- F. None of above. chosen
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.