Triple
T36578855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 5 |
E902332
|
entity |
| Predicate | crewTransferResult |
P186521
|
FINISHED |
| Object | two cosmonauts returned to Earth aboard Soyuz 4 |
—
|
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: two cosmonauts returned to Earth aboard Soyuz 4 | Statement: [Soyuz 5, crewTransferResult, two cosmonauts returned to Earth aboard Soyuz 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransferResult Context triple: [Soyuz 5, crewTransferResult, two cosmonauts returned to Earth aboard Soyuz 4]
-
A.
crewTransferMethod
Indicates the method or means by which crew members are transferred from one location, vehicle, or facility to another.
-
B.
crewTransferToSpacecraft
Indicates the transfer of crew members from one location or vehicle to a specified spacecraft.
-
C.
plannedCrewTransferMethod
Indicates the method or means by which a crew transfer is intended or scheduled to be carried out.
-
D.
crewExchange
Indicates a transfer or replacement of personnel between two crews or crewed entities.
-
E.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:11 p.m.