Triple
T26529501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demo-2 |
E670780
|
entity |
| Predicate | rocketCoreReuse |
P59452
|
FINISHED |
| Object | reused Falcon 9 first stage |
—
|
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: reused Falcon 9 first stage | Statement: [Demo-2, rocketCoreReuse, reused Falcon 9 first stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rocketCoreReuse Context triple: [Demo-2, rocketCoreReuse, reused Falcon 9 first stage]
-
A.
spacecraftReuse
chosen
Indicates that a spacecraft or its components are used for multiple missions or flights instead of being discarded after a single use.
-
B.
spacecraftReuseStatus
Indicates whether a spacecraft has been previously used, is currently being reused, or is intended for reuse.
-
C.
rocketCoreRecovery
Indicates the process or outcome of retrieving and securing the main rocket core after its launch or mission.
-
D.
coreLaunchVehicle
Indicates that one entity serves as the primary launch vehicle used to propel another entity (such as a payload or mission) into space.
-
E.
launchVehicleCoreRecovery
Indicates that the core stage of a launch vehicle is recovered after launch rather than being expended.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:34 a.m.