Triple
T19442178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-21 |
E486375
|
entity |
| Predicate | crewExchange |
P135907
|
FINISHED |
| Object | delivered EO-18 crew to Mir |
—
|
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: delivered EO-18 crew to Mir | Statement: [Soyuz TM-21, crewExchange, delivered EO-18 crew to Mir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewExchange Context triple: [Soyuz TM-21, crewExchange, delivered EO-18 crew to Mir]
-
A.
issExpeditionCrewExchange
Indicates that an event involves the exchange or rotation of crew members on the International Space Station (ISS) between different expeditions.
-
B.
lineupChange
Indicates a modification in the composition or order of participants in a lineup, such as adding, removing, or rearranging members.
-
C.
teamFromTo
Indicates a relationship where a team moves, transfers, or changes affiliation from one entity, location, or organization (the source) to another (the destination).
-
D.
componentExchange
Indicates a relationship where one component provides, transfers, or receives data, energy, or other resources to or from another component.
-
E.
replacedInLineupBy
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63365343081908683c29f6c4c194b |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.