Triple
T9591896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Space and Terrestrial Applications-2 |
E231439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NASA experimental payload |
C919
|
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: NASA experimental payload Context triple: [Office of Space and Terrestrial Applications-2, instanceOf, NASA experimental payload]
-
A.
ISS external payload
An ISS external payload is a scientific or technological instrument package mounted on the outside of the International Space Station to conduct experiments, observations, or demonstrations in the space environment.
-
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.
NASA mission component
chosen
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
D.
NASA space mission
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
E.
NASA research program
A NASA research program is an organized, long-term initiative that systematically investigates specific scientific or technological questions to advance space exploration, Earth observation, or aeronautics capabilities.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:06 p.m.