Triple
T36485563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus External Payload Facility |
E898924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | external payload facility |
C59494
|
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: external payload facility Context triple: [Columbus External Payload Facility, instanceOf, external payload facility]
-
A.
external payload platform
chosen
An external payload platform is a structural interface mounted outside a vehicle or spacecraft that supports, powers, and connects modular instruments or equipment for mission-specific operations.
-
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.
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.
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.
test payload
A test payload is a controlled set of data or content sent through a system or interface to validate functionality, performance, or reliability without affecting real-world operations.
- 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.