Triple
T10999163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocketdyne H-1 |
E259960
|
entity |
| Predicate | propellantMixtureRatio |
P29516
|
FINISHED |
| Object | approximately 2.25:1 O/F |
—
|
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: approximately 2.25:1 O/F | Statement: [Rocketdyne H-1, propellantMixtureRatio, approximately 2.25:1 O/F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellantMixtureRatio Context triple: [Rocketdyne H-1, propellantMixtureRatio, approximately 2.25:1 O/F]
-
A.
propellantRatio
Indicates the proportional relationship between different propellant components used together in a propulsion system.
-
B.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
C.
propellantMass
Indicates the amount of propellant associated with or used by an object or system in a given context.
-
D.
oxidizerToFuelMixtureRatio
chosen
Indicates the proportional amount of oxidizer relative to fuel present in a mixture or system.
-
E.
propellantSecondStage
Indicates that an entity serves as the propellant used in the second stage of a multi-stage propulsion 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d3b08c81909376cd73c42fcefe |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.