Triple
T9867648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 4 |
E239873
|
entity |
| Predicate | crewEVA |
P90961
|
FINISHED |
| Object | no extravehicular activity performed |
—
|
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 extravehicular activity performed | Statement: [Vostok 4, crewEVA, no extravehicular activity performed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewEVA Context triple: [Vostok 4, crewEVA, no extravehicular activity performed]
-
A.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
B.
crewEVAHours
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
-
C.
EVAcrew
Indicates that the subject is a crew member participating in an extravehicular activity (spacewalk).
-
D.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
-
E.
missionCrewStations
Indicates that specific crew stations are assigned or associated with a particular mission.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d209ac8190b9bc9ff017a132da |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:36 p.m.