Triple
T33829367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadalmelik |
E867053
|
entity |
| Predicate | coreFuel |
P177748
|
FINISHED |
| Object | hydrogen-exhausted core |
—
|
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: hydrogen-exhausted core | Statement: [Sadalmelik, coreFuel, hydrogen-exhausted core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreFuel Context triple: [Sadalmelik, coreFuel, hydrogen-exhausted core]
-
A.
coreStageFuel
Indicates that the specified fuel is used in the core stage of a launch vehicle or rocket.
-
B.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
C.
secondaryFuel
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
D.
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.
-
E.
boosterFuel
Indicates that an entity serves as the fuel or propellant used by a booster (such as a rocket booster) to generate thrust.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.