Triple
T1523362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle solid rocket booster joint |
E32279
|
entity |
| Predicate | hasDesignFlaw |
P21734
|
FINISHED |
| Object | susceptibility to O-ring erosion |
—
|
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: susceptibility to O-ring erosion | Statement: [Space Shuttle solid rocket booster joint, hasDesignFlaw, susceptibility to O-ring erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignFlaw Context triple: [Space Shuttle solid rocket booster joint, hasDesignFlaw, susceptibility to O-ring erosion]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignTradeoff
Indicates that one design choice involves compromises or conflicting benefits and drawbacks relative to other possible designs.
-
C.
knownIssue
chosen
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
D.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
-
E.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
- 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.