Triple
T23528880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-14 |
E576506
|
entity |
| Predicate | reentryModuleReturnedCrew |
P127344
|
FINISHED |
| Object | Gennady Padalka |
—
|
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: Gennady Padalka | Statement: [Soyuz TMA-14, reentryModuleReturnedCrew, Gennady Padalka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryModuleReturnedCrew Context triple: [Soyuz TMA-14, reentryModuleReturnedCrew, Gennady Padalka]
-
A.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
-
B.
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.
-
C.
lastCrewReturnDate
Indicates the date on which the most recent crew associated with the entity returned.
-
D.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
E.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.