Triple
T34360599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 18 |
E881860
|
entity |
| Predicate | crewSafetyResult |
P20707
|
FINISHED |
| Object | no fatalities |
—
|
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: no fatalities | Statement: [Soyuz 18, crewSafetyResult, no fatalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSafetyResult Context triple: [Soyuz 18, crewSafetyResult, no fatalities]
-
A.
safetyResponse
Indicates how an entity reacts or what measures it takes in response to a potential or actual safety-related situation.
-
B.
safetyOutcome
Indicates the resulting condition or consequence related to safety that arises from an action, event, or situation.
-
C.
crewOutcome
chosen
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
-
D.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
E.
safetyRequirement
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.