Triple
T21322406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 511 |
E525651
|
entity |
| Predicate | corePropellants |
P21079
|
FINISHED |
| Object | RP-1 and liquid oxygen |
—
|
LITERAL 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: RP-1 and liquid oxygen | Statement: [Atlas V 511, corePropellants, RP-1 and liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corePropellants Context triple: [Atlas V 511, corePropellants, RP-1 and liquid oxygen]
-
A.
propellantComponent
Indicates that one substance serves as a constituent part of a propellant formulation used in a propulsion or thrust-generating system.
-
B.
propellantCombination
chosen
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
C.
propellantForm
Indicates the physical or chemical form in which a propellant is present or used in a system.
-
D.
solidBoosterPropellantType
Indicates the type or composition of propellant used in a solid rocket booster.
-
E.
propellantTypeFirstSecondStages
Indicates that the first and second stages of a launch vehicle use the specified type of propellant.
- F. None of above.
Provenance (3 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed355cc8190a305c1c48117fb9e |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:40 p.m.