Triple
T10058558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle |
E208923
|
entity |
| Predicate | solidBoosterPropellant |
P30125
|
FINISHED |
| Object | ammonium perchlorate composite propellant |
—
|
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: ammonium perchlorate composite propellant | Statement: [Space Shuttle, solidBoosterPropellant, ammonium perchlorate composite propellant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solidBoosterPropellant Context triple: [Space Shuttle, solidBoosterPropellant, ammonium perchlorate composite propellant]
-
A.
solidBoosterPropellantType
chosen
Indicates the type or composition of propellant used in a solid rocket booster.
-
B.
solidRocketBoosters
Indicates that an entity is equipped with or uses solid rocket boosters as part of its propulsion system.
-
C.
propellantTypeCoreStage
Indicates the type of propellant used in the core stage of a launch vehicle or rocket 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfb0f17c8190a8c0cfb02863537d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.