Triple
T1844827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Orbit |
E41260
|
entity |
| Predicate | firstLaunchAttemptOutcome |
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: [Virgin Orbit, firstLaunchAttemptOutcome, failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchAttemptOutcome Context triple: [Virgin Orbit, firstLaunchAttemptOutcome, failure]
-
A.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
B.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
C.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
-
D.
launchOutcome
chosen
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
E.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.