Triple
T17173725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Juno mission to Mir |
E416802
|
entity |
| Predicate | crewRole_SergeiKrikalev |
P126373
|
FINISHED |
| Object | flight engineer |
—
|
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: flight engineer | Statement: [Project Juno mission to Mir, crewRole_SergeiKrikalev, flight engineer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRole_SergeiKrikalev Context triple: [Project Juno mission to Mir, crewRole_SergeiKrikalev, flight engineer]
-
A.
cosmonautName
Indicates that the predicate specifies the personal name associated with a given cosmonaut.
-
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.
crewOfVoskhod2
Indicates that the subject is a member of the crew of the Voskhod 2 space mission.
-
D.
crewOfVoskhod1
Indicates the relationship of being a member of the crew assigned to the Voskhod 1 space mission.
-
E.
astronautFullName
Indicates the complete personal name of an astronaut, typically including given, middle, and family names.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0b7c9c819082e503cb493d7e7b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:37 a.m.