Triple
T26529685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 64 |
E670784
|
entity |
| Predicate | includedRussianCrewMembers |
P193180
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Expedition 64, includedRussianCrewMembers, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedRussianCrewMembers Context triple: [Expedition 64, includedRussianCrewMembers, 2]
-
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.
includedUSCrewMembers
Indicates that the subject entity had U.S. crew members counted as part of its personnel or participants.
-
C.
crewOfVoskhod1
Indicates the relationship of being a member of the crew assigned to the Voskhod 1 space mission.
-
D.
crewOfVoskhod2
Indicates that the subject is a member of the crew of the Voskhod 2 space mission.
-
E.
missionRoleCrew-1
Indicates that a crew member participates in a mission in a specific operational role or capacity.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: April 27, 2026, 1:34 a.m.