Triple
T12598961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 0 |
E300806
|
entity |
| Predicate | failureResult |
P12733
|
FINISHED |
| Object | did not achieve Earth orbit |
—
|
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: did not achieve Earth orbit | Statement: [Pioneer 0, failureResult, did not achieve Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureResult Context triple: [Pioneer 0, failureResult, did not achieve Earth orbit]
-
A.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
D.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
E.
missionFailure
chosen
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:09 p.m.