Triple
T35038485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 400 series |
E1010995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Atlas V configuration |
C29283
|
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: Atlas V configuration Context triple: [Atlas V 400 series, instanceOf, Atlas V configuration]
-
A.
rocket configuration
chosen
A rocket configuration is the defined arrangement and specification of a launch vehicle’s stages, propulsion systems, structural components, and payload interfaces that together determine its performance and mission capabilities.
-
B.
spacecraft configuration
A spacecraft configuration is the specific arrangement and integration of a spacecraft’s structural, propulsion, power, thermal, communication, and payload subsystems designed to meet defined mission objectives and constraints.
-
C.
Gulfstream V variant
A Gulfstream V variant is a specific model or configuration of the long-range, large-cabin Gulfstream V business jet, modified to meet particular performance, mission, or customer requirements.
-
D.
X-plane
An X-plane is an experimental aircraft designed to test and demonstrate new aviation technologies, configurations, or performance capabilities beyond those of conventional aircraft.
-
E.
Apollo spacecraft variant
An Apollo spacecraft variant is a specific configuration or modification of the Apollo command and service modules, and sometimes the lunar module, tailored to different mission profiles, technological updates, or experimental objectives within the Apollo program.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.