Triple
T37720422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew Dragon In-Flight Abort Test |
E939567
|
entity |
| Predicate | boosterFate |
P3146
|
FINISHED |
| Object | destroyed in-flight |
—
|
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: destroyed in-flight | Statement: [Crew Dragon In-Flight Abort Test, boosterFate, destroyed in-flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boosterFate Context triple: [Crew Dragon In-Flight Abort Test, boosterFate, destroyed in-flight]
-
A.
usedWithBoosters
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
-
B.
boosterName
Indicates the name or designation assigned to a booster component associated with an entity or event.
-
C.
boosterType
Indicates the specific kind or category of booster associated with an entity or action.
-
D.
boosterFuel
Indicates that an entity serves as the fuel or propellant used by a booster (such as a rocket booster) to generate thrust.
-
E.
fate
chosen
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.