Triple
T27609733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-7 |
E700279
|
entity |
| Predicate | returnCrew |
P127344
|
FINISHED |
| Object | returned part of Mir resident crew to Earth |
—
|
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: returned part of Mir resident crew to Earth | Statement: [Soyuz TM-7, returnCrew, returned part of Mir resident crew to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnCrew Context triple: [Soyuz TM-7, returnCrew, returned part of Mir resident crew to Earth]
-
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.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
D.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
E.
commandCrew
Indicates that one entity holds command authority over the crew associated with another entity.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:10 p.m.