Triple
T35003487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 3 |
E1009746
|
entity |
| Predicate | secondCrewedMissionOutcome |
P128267
|
FINISHED |
| Object | docking failure |
—
|
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: docking failure | Statement: [Salyut 3, secondCrewedMissionOutcome, docking failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCrewedMissionOutcome Context triple: [Salyut 3, secondCrewedMissionOutcome, docking failure]
-
A.
secondCrewedMission
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.
crewOutcome
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
-
D.
mannedFlightOutcome
chosen
Indicates the result or status of a crewed (manned) spaceflight mission, such as success, failure, or partial success.
-
E.
secondaryDutyAboardVoyager
Indicates that an entity has a secondary, non-primary duty assignment aboard the starship Voyager.
- 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_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.