Triple
T11885893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX COTS Demo Flight 1 |
E282779
|
entity |
| Predicate | recoveryType |
P19129
|
FINISHED |
| Object | ocean splashdown |
—
|
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: ocean splashdown | Statement: [SpaceX COTS Demo Flight 1, recoveryType, ocean splashdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryType Context triple: [SpaceX COTS Demo Flight 1, recoveryType, ocean splashdown]
-
A.
recoverySystem
Indicates a system or mechanism responsible for restoring a previous state, function, or data after a failure, loss, or disruption.
-
B.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
C.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
D.
restorationType
Indicates the specific kind or category of restoration applied to an entity, such as the method, scope, or approach used to return it to a prior or improved state.
-
E.
recoveryConfiguration
Indicates a configuration relationship specifying how an entity should be restored, recovered, or brought back to an operational state after failure or disruption.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a13370819086386fecb99e4f0b |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.