Triple
T36485375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Payload Rack |
E898920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standardized payload carrier |
C31089
|
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: standardized payload carrier Context triple: [International Standard Payload Rack, instanceOf, standardized payload carrier]
-
A.
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.
-
B.
standardized battery pack
A standardized battery pack is a modular, interchangeable energy storage unit designed with uniform specifications to ensure compatibility across multiple devices or systems.
-
C.
payload specialist
A payload specialist is a mission-specific crew member, often not a career astronaut, selected for their expertise in operating, managing, or conducting experiments with particular payloads on a spaceflight.
-
D.
spacecraft payload adapter
A spacecraft payload adapter is a structural interface that securely connects a satellite or payload to the launch vehicle, ensuring proper alignment, load transfer, and separation during ascent and deployment.
-
E.
modular load-carrying system
chosen
A modular load-carrying system is a configurable assembly of interchangeable components designed to transport, support, and adapt to varying types and amounts of loads in different operational contexts.
- 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.