Triple
T37763372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-191 |
E941344
|
entity |
| Predicate | fuelMixture |
P189013
|
FINISHED |
| Object | LOX/RP-1 |
—
|
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: LOX/RP-1 | Statement: [RD-191, fuelMixture, LOX/RP-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelMixture Context triple: [RD-191, fuelMixture, LOX/RP-1]
-
A.
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.
-
B.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
-
C.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
D.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or system.
-
E.
oxidizerToFuelMixtureRatio
Indicates the proportional amount of oxidizer relative to fuel present in a mixture or system.
- F. None of above. chosen
Provenance (4 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.