Triple
T18587754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-9 |
E454281
|
entity |
| Predicate | firstStageRecovery |
P132683
|
FINISHED |
| Object | successful |
—
|
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 | Statement: [SpaceX CRS-9, firstStageRecovery, successful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStageRecovery Context triple: [SpaceX CRS-9, firstStageRecovery, successful]
-
A.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
B.
firstStageReusability
Indicates whether the first stage of a launch vehicle is designed to be recovered and reused after flight.
-
C.
firstStageDescription
Indicates that the value provides a textual explanation or summary of the initial or earliest stage in a multi-stage process or sequence.
-
D.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
E.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b2f20481908da74447cd08d5bd |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.