Triple
T29971866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 2 |
E761337
|
entity |
| Predicate | crewLandingMethod |
P14975
|
FINISHED |
| Object | parachute landing separate from capsule |
—
|
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: parachute landing separate from capsule | Statement: [Vostok 2, crewLandingMethod, parachute landing separate from capsule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLandingMethod Context triple: [Vostok 2, crewLandingMethod, parachute landing separate from capsule]
-
A.
crewLandingStatus
Indicates the status or outcome of a crew’s landing event, such as whether and how the crew has successfully landed.
-
B.
landingMethod
chosen
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
C.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
D.
crewLandingDuration
Indicates the length of time a crewed mission spends on the surface after landing before departure or ascent.
-
E.
landingMethodFirstStage
Indicates the method by which the first stage of a launch vehicle returns and lands after separation.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786ee1608190ad7cf42111f2b7df |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:32 p.m.