Triple
T1979785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSF-44 |
E42997
|
entity |
| Predicate | boosterSideCoreRecovery |
P14984
|
FINISHED |
| Object | successful landing of side boosters |
—
|
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: successful landing of side boosters | Statement: [USSF-44, boosterSideCoreRecovery, successful landing of side boosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boosterSideCoreRecovery Context triple: [USSF-44, boosterSideCoreRecovery, successful landing of side boosters]
-
A.
boosterRecoveryMethod
chosen
Indicates the method or process used to recover a rocket booster after its mission.
-
B.
boosterType
Indicates the specific kind or category of booster associated with an entity or action.
-
C.
boosterSegmentsPerBooster
Indicates the number of segments that make up each individual booster.
-
D.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
E.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:36 p.m.