Triple
T35003486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 3 |
E1009746
|
entity |
| Predicate | secondCrewedMissionAttempt |
P146820
|
FINISHED |
| Object | Soyuz 15 |
—
|
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 15 | Statement: [Salyut 3, secondCrewedMissionAttempt, Soyuz 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCrewedMissionAttempt Context triple: [Salyut 3, secondCrewedMissionAttempt, Soyuz 15]
-
A.
secondCrewedMission
chosen
Indicates that the mission is the second one to carry a crew.
-
B.
secondSoloCrewedDescentVehicle
Indicates that the subject is the second crewed descent vehicle used for a solo mission relative to other such vehicles.
-
C.
launchDateOfSecondCrewedFlight
Indicates the calendar date on which the second crewed flight associated with a given mission or vehicle is launched.
-
D.
secondReplacementMission
Indicates that an entity undertakes or is assigned to a second mission specifically intended to replace or relieve a prior mission or its participants.
-
E.
secondFlightLaunchSite
Indicates the location from which an entity’s second flight or launch is carried out.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:01 p.m.