Triple
T31921187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 27 |
E814972
|
entity |
| Predicate | crewExchangeVehicle |
P124144
|
FINISHED |
| Object | Soyuz TMA-01M |
—
|
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: Soyuz TMA-01M | Statement: [Expedition 27, crewExchangeVehicle, Soyuz TMA-01M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewExchangeVehicle Context triple: [Expedition 27, crewExchangeVehicle, Soyuz TMA-01M]
-
A.
crewExchange
Indicates a transfer or replacement of personnel between two crews or crewed entities.
-
B.
issExpeditionCrewExchange
chosen
Indicates that an event involves the exchange or rotation of crew members on the International Space Station (ISS) between different expeditions.
-
C.
relaunchVehicle
Indicates restarting or sending a vehicle back into operation after it has been stopped, deactivated, or previously launched.
-
D.
intendedCrewVehicle
Indicates that a particular vehicle is designated or planned to be used by a specific crew.
-
E.
replacedRollingStock
Indicates that one rolling stock asset has been substituted or superseded by another in service or operational use.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1f63a40819080e51743627059c7 |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.