Triple
T32524495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 3 |
E831270
|
entity |
| Predicate | crewStatusAfterLanding |
P70692
|
FINISHED |
| Object | survived |
—
|
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: survived | Statement: [Vostok 3, crewStatusAfterLanding, survived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewStatusAfterLanding Context triple: [Vostok 3, crewStatusAfterLanding, survived]
-
A.
crewLandingStatus
chosen
Indicates the status or outcome of a crew’s landing event, such as whether and how the crew has successfully landed.
-
B.
crewLandingDuration
Indicates the length of time a crewed mission spends on the surface after landing before departure or ascent.
-
C.
communicationAfterLanding
Indicates that a communication event occurs after a landing has taken place.
-
D.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
-
E.
lastCrewedLandingDate
Indicates the calendar date on which the most recent crewed landing associated with the subject took place.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c516640c81909fce8dc8240a00a9 |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.