Triple
T37030936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E916490
|
entity |
| Predicate | lastLaunchOutcome |
P21238
|
FINISHED |
| Object | failure |
—
|
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: failure | Statement: [LauncherOne, lastLaunchOutcome, failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastLaunchOutcome Context triple: [LauncherOne, lastLaunchOutcome, failure]
-
A.
lastLaunchDate
Indicates the date on which the most recent launch event associated with an entity occurred.
-
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.
lastLaunchPayload
Indicates the payload that was carried on the most recent launch associated with the given entity.
-
D.
lastRun
Indicates the most recent time or instance at which a particular process, task, or action was executed.
-
E.
launchStatus
Indicates the current state or phase of a launch process, such as whether it is planned, in progress, successful, or failed.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.