Triple
T11692469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COTS Demo Flight 1 |
E277901
|
entity |
| Predicate | landingRecovery |
P101290
|
FINISHED |
| Object | recovered by SpaceX recovery team |
—
|
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: recovered by SpaceX recovery team | Statement: [COTS Demo Flight 1, landingRecovery, recovered by SpaceX recovery team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingRecovery Context triple: [COTS Demo Flight 1, landingRecovery, recovered by SpaceX recovery team]
-
A.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
B.
landingMass
Indicates the mass of an object or vehicle at the moment it lands.
-
C.
typeOfLanding
Indicates the specific kind or category of landing that occurs in a given event or situation.
-
D.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
E.
landingOperation
Indicates an operation in which an aircraft, spacecraft, or similar vehicle descends and makes contact with a surface to complete its landing.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.