Triple
T7492091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares I-X |
E177028
|
entity |
| Predicate | launchAbortSystem |
P77847
|
FINISHED |
| Object | simulated launch abort system mass simulator |
—
|
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: simulated launch abort system mass simulator | Statement: [Ares I-X, launchAbortSystem, simulated launch abort system mass simulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAbortSystem Context triple: [Ares I-X, launchAbortSystem, simulated launch abort system mass simulator]
-
A.
launchEscapeSystem
Indicates initiating or activating an emergency mechanism designed to rapidly propel occupants or payload away from a vehicle or structure to ensure their safety.
-
B.
abortSystemType
Indicates that a system or process is terminated or halted based on its specific type or classification.
-
C.
launchVehicleCoreRecovery
Indicates that the core stage of a launch vehicle is recovered after launch rather than being expended.
-
D.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
launchAndRecovery
Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
- F. None of above. chosen
Provenance (4 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:43 p.m.