Triple
T29998614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Launch program |
E762098
|
entity |
| Predicate | notableFailureCause |
—
|
GENERATED |
| Object | RD-171M engine failure |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFailureCause Context triple: [Sea Launch program, notableFailureCause, RD-171M engine failure]
-
A.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
notableProtectiveFailure
Indicates a relationship where an entity’s protective role or safeguards significantly failed, leading to a notable or consequential breakdown in protection.
-
C.
notableException
Indicates that something or someone stands out as an unusual or noteworthy deviation from an expected pattern, rule, or general case.
-
D.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
-
E.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
- F. None of above.
Provenance (1 batch)
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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:40 p.m.