Triple
T26727311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAM-D stage failed to provide required velocity |
E673867
|
entity |
| Predicate | failureOutcome |
P159544
|
FINISHED |
| Object | Westar 6 not reaching planned geostationary orbit by itself |
—
|
NE NERFINISHED |
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: Westar 6 not reaching planned geostationary orbit by itself | Statement: [PAM-D stage failed to provide required velocity, failureOutcome, Westar 6 not reaching planned geostationary orbit by itself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureOutcome Context triple: [PAM-D stage failed to provide required velocity, failureOutcome, Westar 6 not reaching planned geostationary orbit by itself]
-
A.
failureEffect
chosen
Indicates the resulting condition, consequence, or outcome that occurs when a failure happens.
-
B.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
C.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
D.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
E.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6180c6ba081908b82e0a76fdb94e8 |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:43 a.m.