Triple
T34714291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-13M |
E1000729
|
entity |
| Predicate | missionRoleOfAlexanderGerst |
P173483
|
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: [Soyuz TMA-13M, missionRoleOfAlexanderGerst, flight engineer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionRoleOfAlexanderGerst Context triple: [Soyuz TMA-13M, missionRoleOfAlexanderGerst, flight engineer]
-
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.
missionSpecialist
Indicates that an entity serves in the role of a mission specialist in relation to a particular mission or spaceflight.
-
D.
spaceStationRole
Indicates the functional role or duty an entity has in relation to a space station.
-
E.
missionCrewRole
chosen
Indicates the specific role or function an individual holds as a member of a mission’s crew.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 3:59 p.m.