Triple
T19307722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continuous Flow Electrophoresis System |
E482883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | microgravity experiment payload |
C37443
|
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: microgravity experiment payload Context triple: [Continuous Flow Electrophoresis System, instanceOf, microgravity experiment payload]
-
A.
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.
-
B.
space experiment
A space experiment is a controlled scientific investigation conducted in the unique conditions of outer space or microgravity to study physical, biological, or technological phenomena not observable or easily replicated on Earth.
-
C.
scientific payload
chosen
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.
-
D.
Spacelab subsystem
A Spacelab subsystem is a distinct functional component of the Spacelab space laboratory that performs specialized tasks—such as power, life support, data handling, or experiment support—to enable and sustain scientific operations in orbit.
-
E.
Space Shuttle payload
A Space Shuttle payload is any cargo, equipment, satellite, experiment, or module carried in the Shuttle’s payload bay to be deployed, operated, or returned from space.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:32 p.m.