Triple
T7918844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Functional Cargo Block |
E183892
|
entity |
| Predicate | primaryPropellants |
P42806
|
FINISHED |
| Object | UDMH |
—
|
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: UDMH | Statement: [Functional Cargo Block, primaryPropellants, UDMH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPropellants Context triple: [Functional Cargo Block, primaryPropellants, UDMH]
-
A.
solidBoosterPropellantType
Indicates the type or composition of propellant used in a solid rocket booster.
-
B.
usesPropellantType
chosen
Indicates that one entity operates or functions using a specific type of propellant as its fuel or reaction mass.
-
C.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
D.
propellantTypeUpperStage
Indicates the type of propellant used by the upper stage of a launch vehicle or rocket system.
-
E.
propellantFirstStage
Indicates that the specified propellant is used in the first stage of a multi-stage 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.