Triple
T1523679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiokol |
E32285
|
entity |
| Predicate | responsibilityInAccident |
P636
|
FINISHED |
| Object | design and manufacture of SRB field joint O-rings |
—
|
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: design and manufacture of SRB field joint O-rings | Statement: [Thiokol, responsibilityInAccident, design and manufacture of SRB field joint O-rings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibilityInAccident Context triple: [Thiokol, responsibilityInAccident, design and manufacture of SRB field joint O-rings]
-
A.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
B.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
C.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
D.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
E.
siteOfAccident
Indicates the location where an accident occurred.
- 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.