Triple
T28243183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-32 |
E712087
|
entity |
| Predicate | replacedByOnISS |
P179480
|
FINISHED |
| Object | Soyuz TM-33 |
—
|
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 TM-33 | Statement: [Soyuz TM-32, replacedByOnISS, Soyuz TM-33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByOnISS Context triple: [Soyuz TM-32, replacedByOnISS, Soyuz TM-33]
-
A.
broughtToISS
Indicates that an object or entity was transported or delivered to the International Space Station (ISS).
-
B.
installedOnISSDate
Indicates the date on which something was installed on the International Space Station (ISS).
-
C.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
-
D.
wasFirstISSModuleLaunched
Indicates that the subject module was the first module of the International Space Station to be launched into orbit.
-
E.
dockingWithISS
Indicates a relationship where a spacecraft is physically connecting and securing itself to the International Space Station to enable transfer of crew, cargo, or resources.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 10:59 p.m.