Triple
T35589399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voskhod 2 |
E1028450
|
entity |
| Predicate | EVAChallenge |
P183428
|
FINISHED |
| Object | difficulty re-entering airlock due to suit overinflation |
—
|
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: difficulty re-entering airlock due to suit overinflation | Statement: [Voskhod 2, EVAChallenge, difficulty re-entering airlock due to suit overinflation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAChallenge Context triple: [Voskhod 2, EVAChallenge, difficulty re-entering airlock due to suit overinflation]
-
A.
EVAobjective
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
B.
EVAparticipant
Indicates participation of an entity in an extravehicular activity (EVA), such as being one of the actors involved in a spacewalk.
-
C.
EVAcrew
Indicates that the subject is a crew member participating in an extravehicular activity (spacewalk).
-
D.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
E.
EVAstartDate
Indicates the date on which an extravehicular activity (EVA) begins.
- F. None of above. chosen
Provenance (4 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.