Triple
T17390961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 551 |
E422820
|
entity |
| Predicate | coreStagePropellants |
P42906
|
FINISHED |
| Object | RP-1/LOX |
—
|
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/LOX | Statement: [Atlas V 551, coreStagePropellants, RP-1/LOX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreStagePropellants Context triple: [Atlas V 551, coreStagePropellants, RP-1/LOX]
-
A.
propellantTypeFirstSecondStages
Indicates that the first and second stages of a launch vehicle use the specified type of propellant.
-
B.
propellantComponent
Indicates that one substance serves as a constituent part of a propellant formulation used in a propulsion or thrust-generating system.
-
C.
fourthStagePropellant
Indicates that the specified propellant is used in the fourth stage of a multi-stage rocket or launch vehicle.
-
D.
thirdStagePropellant
Indicates that an entity serves as the propellant used in the third stage of a multi-stage rocket or launch vehicle.
-
E.
propellantTypeCoreStage
chosen
Indicates the type of propellant used in the core stage of a launch vehicle or rocket system.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ab950d4819098d6a46f67c46191 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.