Triple
T37093061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-111 |
E918477
|
entity |
| Predicate | issCrewMemberReturned |
P127344
|
FINISHED |
| Object | Yuri Onufrienko |
—
|
NE NERFINISHED |
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: Yuri Onufrienko | Statement: [STS-111, issCrewMemberReturned, Yuri Onufrienko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issCrewMemberReturned Context triple: [STS-111, issCrewMemberReturned, Yuri Onufrienko]
-
A.
returnedCrewMember
chosen
Indicates that a person who was part of a crew has come back from a mission, trip, or assignment to a prior location or status.
-
B.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
-
C.
mirOutgoingCrewMember
Indicates that a person is serving or has served as a departing crew member from the Mir space station.
-
D.
deliveredISSResidentCrewMember
Indicates that an entity transported and brought a crew member to take up residence aboard the International Space Station.
-
E.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.