Triple
T27996819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kestrel engine |
E707033
|
entity |
| Predicate | propellantFeedType |
P39480
|
FINISHED |
| Object | high-pressure helium-fed tanks |
—
|
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: high-pressure helium-fed tanks | Statement: [Kestrel engine, propellantFeedType, high-pressure helium-fed tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellantFeedType Context triple: [Kestrel engine, propellantFeedType, high-pressure helium-fed tanks]
-
A.
propellantFeedSystem
chosen
Indicates a relationship where a system supplies, regulates, or transports propellant to a propulsion or engine unit.
-
B.
propellantFeedGas
Indicates a relationship where a gas is used or supplied as the propellant feed in a propulsion or thruster system.
-
C.
turbopumpType
Indicates the specific kind or classification of turbopump associated with an entity.
-
D.
solidBoosterPropellantType
Indicates the type or composition of propellant used in a solid rocket booster.
-
E.
propellantPhase
Indicates the physical state or phase (e.g., solid, liquid, gas) that the propellant is in under specified 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 7:54 p.m.