Triple
T33081138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Cryogenic Second Stage |
E846509
|
entity |
| Predicate | engineNozzle |
P69407
|
FINISHED |
| Object | extendable carbon-carbon nozzle |
—
|
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: extendable carbon-carbon nozzle | Statement: [Delta Cryogenic Second Stage, engineNozzle, extendable carbon-carbon nozzle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineNozzle Context triple: [Delta Cryogenic Second Stage, engineNozzle, extendable carbon-carbon nozzle]
-
A.
bellNozzle
Indicates a nozzle whose shape flares outward like a bell, typically used to optimize the expansion of exhaust flow.
-
B.
nozzleType
chosen
Indicates the specific kind or category of nozzle associated with or used by an entity.
-
C.
rocketEngine
Indicates that an entity functions as, or is equipped with, a rocket engine used to generate thrust for propulsion.
-
D.
rocketEngineSupplier
Indicates that one entity supplies rocket engines to another entity.
-
E.
nozzleDeflectionRange
Indicates the range of angles through which a nozzle can be deflected from its neutral or reference position.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:26 a.m.