Triple
T17245784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LE-9 |
E418620
|
entity |
| Predicate | mixtureRatio_OxToFuel |
P29516
|
FINISHED |
| Object | about 6 |
—
|
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: about 6 | Statement: [LE-9, mixtureRatio_OxToFuel, about 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mixtureRatio_OxToFuel Context triple: [LE-9, mixtureRatio_OxToFuel, about 6]
-
A.
oxidizerToFuelMixtureRatio
chosen
Indicates the proportional amount of oxidizer relative to fuel present in a mixture or system.
-
B.
propellantRatio
Indicates the proportional relationship between different propellant components used together in a propulsion system.
-
C.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
-
D.
fuelEnrichment
Indicates the degree to which a fuel has been processed to increase the concentration of its active or fissile component relative to its natural state.
-
E.
oxidizerRich
Indicates that a reaction mixture or combustion process contains a higher proportion of oxidizer than fuel, resulting in oxidizer-rich conditions.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.