Triple
T29971870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 2 |
E761337
|
entity |
| Predicate | crewCallsGhermanTitovRole |
P168722
|
FINISHED |
| Object | pilot-cosmonaut |
—
|
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: pilot-cosmonaut | Statement: [Vostok 2, crewCallsGhermanTitovRole, pilot-cosmonaut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCallsGhermanTitovRole Context triple: [Vostok 2, crewCallsGhermanTitovRole, pilot-cosmonaut]
-
A.
crewRole_SergeiKrikalev
Indicates that there is a specified crew role or position associated with Sergei Krikalev within a particular mission or crew context.
-
B.
crewRoleOf_Valentina Tereshkova
Indicates that a specified crew role is held by, or associated with, Valentina Tereshkova within a particular mission or context.
-
C.
cosmonautName
Indicates that the predicate specifies the personal name associated with a given cosmonaut.
-
D.
crewOfVoskhod2
Indicates that the subject is a member of the crew of the Voskhod 2 space mission.
-
E.
crewMemberRole_JohnGlenn
Indicates that John Glenn holds or held a specific role or position as a member of a crew.
- 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_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_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:32 p.m.