Triple
T10211955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IV |
E242349
|
entity |
| Predicate | rocketEngineType |
P24153
|
FINISHED |
| Object | hypergolic liquid-fueled core stages |
—
|
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: hypergolic liquid-fueled core stages | Statement: [Titan IV, rocketEngineType, hypergolic liquid-fueled core stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rocketEngineType Context triple: [Titan IV, rocketEngineType, hypergolic liquid-fueled core stages]
-
A.
rocketEngine
Indicates that an entity functions as, or is equipped with, a rocket engine used to generate thrust for propulsion.
-
B.
standardRocketMotor
Indicates that an entity functions as a standard rocket motor used for propulsion in a rocket system.
-
C.
turbopumpType
Indicates the specific kind or classification of turbopump associated with an entity.
-
D.
propulsionTypeUpperStage
Indicates the kind of propulsion system used by the upper stage of a multi-stage vehicle or rocket.
-
E.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa23bce881909b5deac612ec22cb |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:02 a.m.