Triple
T38187963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars 5 |
E1005371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet Mars spacecraft |
C37760
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Soviet Mars spacecraft Context triple: [Mars 5, instanceOf, Soviet Mars spacecraft]
-
A.
Soyuz programme mission
A Soyuz programme mission is a spaceflight conducted under the Soviet and later Russian Soyuz program, typically involving crewed or uncrewed launches using Soyuz spacecraft and rockets for orbital operations such as transport to space stations, scientific research, or satellite deployment.
-
B.
Mars orbiter payload
A Mars orbiter payload is the collection of scientific instruments, sensors, and supporting hardware carried by a spacecraft in Mars orbit to observe, measure, and transmit data about the planet’s atmosphere, surface, interior, and space environment.
-
C.
Mars system mission
chosen
A Mars system mission is a spaceflight endeavor designed to explore Mars and its surrounding environment, including its moons, atmosphere, surface, and potential for past or present life.
-
D.
Mars mission element
A Mars mission element is a distinct component, system, or phase of a Mars exploration mission (such as spacecraft, landers, habitats, or support infrastructure) that contributes specific functions toward achieving the mission’s overall objectives.
-
E.
Mars rover instrument
A Mars rover instrument is a specialized scientific device mounted on a Mars rover that measures, analyzes, or images the Martian environment and geology to support planetary research and exploration objectives.
- F. None of above.
Provenance (1 batch)
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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:29 p.m.