Triple
T33369269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 41 |
E854438
|
entity |
| Predicate | supportsLaunchConfiguration |
P206435
|
FINISHED |
| Object | Atlas V 400 series |
E1010995
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Atlas V 400 series | Statement: [Space Launch Complex 41, supportsLaunchConfiguration, Atlas V 400 series]
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 (5 batches)
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. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36117d62d08190b6a9e15968ae5145 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:35 a.m.