Triple
T16303550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Automated Transfer Vehicle program |
E395848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | uncrewed cargo spacecraft program |
C14432
|
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: uncrewed cargo spacecraft program Context triple: [European Automated Transfer Vehicle program, instanceOf, uncrewed cargo spacecraft program]
-
A.
space station resupply vehicle
chosen
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
-
B.
uncrewed spaceflight
Uncrewed spaceflight is the operation of spacecraft without human passengers onboard, using automated systems and remote control to conduct missions such as exploration, observation, and technology testing in space.
-
C.
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.
-
D.
space launch vehicle development program
A space launch vehicle development program is an organized, multi-phase effort to design, test, and qualify rockets and associated systems for reliably delivering payloads from Earth to space.
-
E.
NASA spacecraft program
A NASA spacecraft program is an organized initiative that designs, develops, launches, and operates one or more spacecraft to achieve specific scientific, exploratory, or technological objectives in space.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.