Triple
T22478031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51-F |
E555685
|
entity |
| Predicate | mainEngineShutdownCause |
P148357
|
FINISHED |
| Object | fault in one Space Shuttle Main Engine |
—
|
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: fault in one Space Shuttle Main Engine | Statement: [STS-51-F, mainEngineShutdownCause, fault in one Space Shuttle Main Engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEngineShutdownCause Context triple: [STS-51-F, mainEngineShutdownCause, fault in one Space Shuttle Main Engine]
-
A.
centerEngineShutdown
Indicates that the central engine in a multi-engine system has been turned off or has ceased operating.
-
B.
designedToAllowShutdownOf
Indicates that one entity is specifically created or configured to enable the shutdown or power-off of another entity.
-
C.
firstLongShutdown
Indicates the first occurrence of a prolonged shutdown event affecting the referenced entity or system.
-
D.
permanentShutdown
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
E.
secondLongShutdown
Indicates that an entity undergoes a second extended or prolonged shutdown event in a sequence of shutdowns.
- F. None of above. chosen
Provenance (4 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be58ed08190b88706a7cb85616b |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.