Triple
T28030270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-13 |
E708244
|
entity |
| Predicate | crewExchangeFunction |
P135907
|
FINISHED |
| Object | returned previous Mir 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 previous Mir crew to Earth | Statement: [Soyuz TM-13, crewExchangeFunction, returned previous Mir crew to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewExchangeFunction Context triple: [Soyuz TM-13, crewExchangeFunction, returned previous Mir crew to Earth]
-
A.
crewExchange
chosen
Indicates a transfer or replacement of personnel between two crews or crewed entities.
-
B.
issExpeditionCrewExchange
Indicates that an event involves the exchange or rotation of crew members on the International Space Station (ISS) between different expeditions.
-
C.
componentExchange
Indicates a relationship where one component provides, transfers, or receives data, energy, or other resources to or from another component.
-
D.
crewUser
Indicates that a user is a member of, or assigned as part of, a specific crew.
-
E.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:15 p.m.