Triple
T37030931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E916490
|
entity |
| Predicate | firstLaunchFailureCause |
P21234
|
FINISHED |
| Object | propellant line rupture in 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: propellant line rupture in first stage | Statement: [LauncherOne, firstLaunchFailureCause, propellant line rupture in first stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchFailureCause Context triple: [LauncherOne, firstLaunchFailureCause, propellant line rupture in first stage]
-
A.
failureCauseOnFirstFlight
chosen
Indicates that an entity’s first flight resulted in a failure and specifies the cause of that failure.
-
B.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
C.
firstLaunchMission
Indicates that a mission is the first launch associated with a particular object, program, or entity.
-
D.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
-
E.
secondLaunchOutcome
Indicates the result or status of the entity’s second launch attempt or event.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.