Triple
T464437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship launch system |
E8413
|
entity |
| Predicate | upperStageRecoveryMethod |
P14985
|
FINISHED |
| Object | vertical propulsive landing |
—
|
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: vertical propulsive landing | Statement: [Starship launch system, upperStageRecoveryMethod, vertical propulsive landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperStageRecoveryMethod Context triple: [Starship launch system, upperStageRecoveryMethod, vertical propulsive landing]
-
A.
upperStageType
Indicates the type or classification of the upper stage in a multi-stage system or structure.
-
B.
upperStageStructure
Indicates that one entity functions as the upper structural stage or upper-level framework component of another entity.
-
C.
enginesUpperStage
Indicates that the specified engines are part of, or belong to, the upper stage of a multi-stage launch vehicle or rocket.
-
D.
fuelUpperStage
Indicates that an agent supplies or loads propellant into the upper stage of a launch vehicle or rocket.
-
E.
landingMethodFirstStage
Indicates the method by which the first stage of a launch vehicle returns and lands after separation.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd5b6b48190ae23968135cf6417 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.