Triple
T33369269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 41 |
E854438
|
entity |
| Predicate | supportsLaunchConfiguration |
—
|
GENERATED |
| Object | Atlas V 400 series |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLaunchConfiguration Context triple: [Space Launch Complex 41, supportsLaunchConfiguration, Atlas V 400 series]
-
A.
launchesSupported
Indicates that one entity is capable of initiating or starting another entity or process.
-
B.
plannedLaunchConfiguration
Indicates that there is a specified configuration or setup intended to be used for a future launch event or operation.
-
C.
supportsRuntimeConfiguration
Indicates that one entity allows its behavior or settings to be adjusted dynamically while the system is running.
-
D.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
E.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.