Triple
T34402984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 21 |
E883030
|
entity |
| Predicate | returnTransportRole |
P187601
|
FINISHED |
| Object | returned crew from Salyut 5 |
—
|
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: returned crew from Salyut 5 | Statement: [Soyuz 21, returnTransportRole, returned crew from Salyut 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnTransportRole Context triple: [Soyuz 21, returnTransportRole, returned crew from Salyut 5]
-
A.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
B.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
C.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
-
D.
definesTransportFor
Indicates that one entity specifies or determines the means, method, or system of transport used by another entity.
-
E.
returnedToRole
Indicates that an entity resumed or went back to a role or position it previously held.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: May 1, 2026, 1:59 a.m.