Triple
T1979784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSF-44 |
E42997
|
entity |
| Predicate | rocketCoreRecovery |
P35734
|
FINISHED |
| Object | no core recovery |
—
|
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: no core recovery | Statement: [USSF-44, rocketCoreRecovery, no core recovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rocketCoreRecovery Context triple: [USSF-44, rocketCoreRecovery, no core recovery]
-
A.
upperStageRecoveryMethod
Indicates the method or technique used to recover the upper stage of a launch vehicle after its mission.
-
B.
solidRocketBoosters
Indicates that an entity is equipped with or uses solid rocket boosters as part of its propulsion system.
-
C.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
D.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
E.
firstCommercialSpacecraftToReturnFromOrbit
Indicates that the subject is the first commercial spacecraft ever to successfully return to Earth from orbit.
- 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_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. |
| PDg | Predicate description generation | batch_69abb96e07c08190beed60096e9d71b4 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:36 p.m.