Triple
T36863303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 11 |
E911001
|
entity |
| Predicate | reentryAccident |
P106631
|
FINISHED |
| Object | cabin depressurization |
—
|
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: cabin depressurization | Statement: [Soyuz 11, reentryAccident, cabin depressurization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryAccident Context triple: [Soyuz 11, reentryAccident, cabin depressurization]
-
A.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
B.
reentryCause
chosen
Indicates the factor, event, or condition that led to or triggered a reentry.
-
C.
reentryRecovery
Indicates the process or capability of safely recovering an object or vehicle after it reenters an atmosphere from space or high-altitude flight.
-
D.
reentryConcern
Indicates a concern or issue related to an entity’s return or reentry into a system, environment, or context after having been outside it.
-
E.
reentryUse
Indicates the use or application of something during a process of reentering a place, state, or system.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.