Triple
T19729307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA–ESA–NASDA collaboration |
E473808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spaceflight program partnership |
C42534
|
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: spaceflight program partnership Context triple: [NASA–ESA–NASDA collaboration, instanceOf, spaceflight program partnership]
-
A.
human spaceflight program
A human spaceflight program is an organized, long-term governmental or commercial initiative that designs, funds, and operates crewed missions beyond Earth’s atmosphere for exploration, research, and related objectives.
-
B.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
C.
spaceflight program phase
A spaceflight program phase is a distinct, time-bounded stage within a space mission or program that groups related objectives, activities, and resources to achieve specific milestones in the overall mission lifecycle.
-
D.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
E.
space launch procurement program
A space launch procurement program is an organized framework through which a government or commercial entity acquires launch services, vehicles, and related support to place payloads into space under defined technical, schedule, and cost requirements.
- F. None of above. chosen
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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.