Triple
T36812232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 10 |
E909624
|
entity |
| Predicate | failureAspect |
P159544
|
FINISHED |
| Object | inability to achieve secure mechanical lock with Salyut 1 |
—
|
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: inability to achieve secure mechanical lock with Salyut 1 | Statement: [Soyuz 10, failureAspect, inability to achieve secure mechanical lock with Salyut 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureAspect Context triple: [Soyuz 10, failureAspect, inability to achieve secure mechanical lock with Salyut 1]
-
A.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
B.
failureReturn
Indicates that an operation or process results in an unsuccessful outcome and returns a corresponding failure value or status.
-
C.
failureEffect
chosen
Indicates the resulting condition, consequence, or outcome that occurs when a failure happens.
-
D.
failureHandledBy
Indicates that a failure or error condition is managed, mitigated, or resolved by a specified handler or mechanism.
-
E.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.