Triple
T27549053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 8 |
E695440
|
entity |
| Predicate | returnTransportSpacecraft |
P93680
|
FINISHED |
| Object | Soyuz TMA-3 |
—
|
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-3 | Statement: [Expedition 8, returnTransportSpacecraft, Soyuz TMA-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnTransportSpacecraft Context triple: [Expedition 8, returnTransportSpacecraft, Soyuz TMA-3]
-
A.
usedCargoSpacecraftType
Indicates that a particular type of cargo spacecraft was employed or utilized in a given mission or context.
-
B.
spacecraftReturn
chosen
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
C.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
D.
backupSpacecraft
Indicates that one spacecraft serves as a backup or redundant counterpart for another spacecraft.
-
E.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 1:34 p.m.