Triple
T276725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 |
E5264
|
entity |
| Predicate | fairingReusability |
P5431
|
FINISHED |
| Object | payload fairings designed for recovery and reuse |
—
|
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: payload fairings designed for recovery and reuse | Statement: [Falcon 9, fairingReusability, payload fairings designed for recovery and reuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fairingReusability Context triple: [Falcon 9, fairingReusability, payload fairings designed for recovery and reuse]
-
A.
fairingType
Indicates the specific kind or design category of a fairing used in a structure, vehicle, or assembly.
-
B.
fairingHeight
Indicates the vertical dimension or distance from base to top of a fairing structure.
-
C.
fairingDiameter
Indicates the diameter measurement of a payload fairing used to enclose or protect an object.
-
D.
reusability
chosen
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
E.
firstStageReusability
Indicates whether the first stage of a launch vehicle is designed to be recovered and reused after flight.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25ded68c88190b1fc595ce329aeb9 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7480e881909399beccfc7ffb81 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.