Triple
T6286137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream |
E140904
|
entity |
| Predicate | launchFailureDetail |
P21238
|
FINISHED |
| Object | missed intended lunar impact due to guidance error |
—
|
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: missed intended lunar impact due to guidance error | Statement: [Dream, launchFailureDetail, missed intended lunar impact due to guidance error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchFailureDetail Context triple: [Dream, launchFailureDetail, missed intended lunar impact due to guidance error]
-
A.
launchFailures
Indicates that attempts to initiate or start an operation, process, or system have failed.
-
B.
launchOutcome
chosen
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
C.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
D.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
-
E.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063fe59fc81908dbd968017771190 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.