Triple
T27609723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-7 |
E700279
|
entity |
| Predicate | spacecraftReturned |
P93680
|
FINISHED |
| Object | Soyuz TM-7 descent module |
—
|
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-7 descent module | Statement: [Soyuz TM-7, spacecraftReturned, Soyuz TM-7 descent module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftReturned Context triple: [Soyuz TM-7, spacecraftReturned, Soyuz TM-7 descent module]
-
A.
spacecraftReturn
chosen
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
B.
cargoSpacecraftVisited
Indicates that a cargo spacecraft has made a visit to a particular location or object.
-
C.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
D.
spacecraft
Indicates that an entity is a vehicle or object designed to travel or operate in outer space.
-
E.
spacecraftServedOn
Indicates that a particular spacecraft is one on which an entity (typically a person) has served or been assigned.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 2:10 p.m.