Triple
T36485448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JEM Exposed Facility |
E898921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unpressurized experiment platform |
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: unpressurized experiment platform Context triple: [JEM Exposed Facility, instanceOf, unpressurized experiment platform]
-
A.
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.
-
B.
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.
-
C.
space capsule
A space capsule is a small, often conical or cylindrical crew or cargo spacecraft designed to survive launch, spaceflight, reentry, and landing while protecting its occupants and equipment.
-
D.
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.
-
E.
unpressurized cargo carrier
An unpressurized cargo carrier is a transport container or vehicle section designed to hold goods in an environment exposed to ambient external pressure, typically used for freight that does not require a controlled or pressurized atmosphere.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.