Triple
T31919551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-80 |
E814930
|
entity |
| Predicate | failedActivity |
P55520
|
FINISHED |
| Object | planned spacewalks canceled due to airlock hatch problem |
—
|
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: planned spacewalks canceled due to airlock hatch problem | Statement: [STS-80, failedActivity, planned spacewalks canceled due to airlock hatch problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failedActivity Context triple: [STS-80, failedActivity, planned spacewalks canceled due to airlock hatch problem]
-
A.
activityEndedBecauseOf
chosen
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
failed
Indicates that an attempted action or process did not succeed in achieving its intended outcome.
-
D.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
E.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1f2f83c819084f7c5dde7d3b1ad |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:02 a.m.