Triple
T22600326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury spacecraft Sigma 7 |
E574796
|
entity |
| Predicate | escapeSystem |
P44180
|
FINISHED |
| Object | launch escape tower |
—
|
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: launch escape tower | Statement: [Mercury spacecraft Sigma 7, escapeSystem, launch escape tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeSystem Context triple: [Mercury spacecraft Sigma 7, escapeSystem, launch escape tower]
-
A.
launchEscapeSystem
chosen
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.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
C.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
D.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
E.
escapeOutcome
Indicates the result or consequence of an attempt to escape, such as whether it succeeded, failed, or led to a particular follow-up state.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626c6ce08190b991e89b12c67a5a |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.