Triple

T17173728
Position Surface form Disambiguated ID Type / Status
Subject Project Juno mission to Mir E416802 entity
Predicate missionNameInRussian P20560 FINISHED
Object Союз ТМ-12 полёт к Мир по программе Джуно 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: Союз ТМ-12 полёт к Мир по программе Джуно | Statement: [Project Juno mission to Mir, missionNameInRussian, Союз ТМ-12 полёт к Мир по программе Джуно]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: missionNameInRussian
Context triple: [Project Juno mission to Mir, missionNameInRussian, Союз ТМ-12 полёт к Мир по программе Джуно]
  • A. missionName
    Indicates the designated title or label assigned to a specific mission or operation.
  • B. originalNameOfMission
    Indicates the original or initial name that was assigned to a mission before any renaming or reclassification.
  • C. nameInRussian chosen
    Indicates that an entity is known or referred to by a specific name when expressed in the Russian language.
  • D. missionNumber
    Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
  • E. currentNameInRussian
    Indicates the current official name of an entity as expressed in the Russian language.
  • 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_69d886d5f34c8190b24564dfaa63f3fb completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3fc0b7c9c819082e503cb493d7e7b completed April 18, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69e3830d2a90819092386717dc56f0e8 completed April 18, 2026, 1:11 p.m.
Created at: April 10, 2026, 5:37 a.m.