Triple

T16405111
Position Surface form Disambiguated ID Type / Status
Subject Salyut space stations E398405 entity
Predicate hasPart P35 FINISHED
Object Salyut 6 E1044672 NE 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: Salyut 6 | Statement: [Salyut space stations, hasPart, Salyut 6]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Salyut 6
Context triple: [Salyut space stations, hasPart, Salyut 6]
  • A. Salyut 6 chosen
    Salyut 6 was a Soviet-era space station that enabled long-duration human spaceflight and pioneered the use of uncrewed cargo resupply missions in low Earth orbit.
  • B. Salyut 7
    Salyut 7 was a Soviet-era modular space station that served as one of the last and most advanced stations in the Salyut program, paving the way for the later Mir space station.
  • C. Salyut 5
    Salyut 5 was a Soviet military Almaz-class space station launched in 1976 for reconnaissance and research in low Earth orbit.
  • D. Salyut 4
    Salyut 4 was a Soviet-era Earth-orbiting space station used primarily for scientific research and astronomical observations in the mid-1970s.
  • E. Salyut 2
    Salyut 2 was a Soviet military space station launched in 1973 as part of the Almaz program, which failed shortly after reaching orbit due to structural and control system problems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d1f16481909adb19dab86dcc72 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007d9c8de4819093ae3901cf0c8805 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:09 a.m.