Triple

T1523378
Position Surface form Disambiguated ID Type / Status
Subject Space Shuttle solid rocket booster joint E32279 entity
Predicate failureMode P9853 FINISHED
Object hot gas leak through primary O-ring 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: hot gas leak through primary O-ring | Statement: [Space Shuttle solid rocket booster joint, failureMode, hot gas leak through primary O-ring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: failureMode
Context triple: [Space Shuttle solid rocket booster joint, failureMode, hot gas leak through primary O-ring]
  • A. missionFailure
    Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
  • B. fault
    Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
  • C. failsWhen
    Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
  • D. decayMode
    Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
  • E. notableProtectiveFailure chosen
    Indicates a relationship where an entity’s protective role or safeguards significantly failed, leading to a notable or consequential breakdown in protection.
  • 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_69a885e9b0ac819093a9806ad0efc82c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93d4756888190bf3872154de11539 completed March 5, 2026, 8:22 a.m.
PD Predicate disambiguation batch_69a907ac7ea081908dd95bb5cc3b9847 completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.