Triple

T17173702
Position Surface form Disambiguated ID Type / Status
Subject Project Juno mission to Mir E416802 entity
Predicate crewMember P2094 FINISHED
Object Anatoly Artsebarsky
Anatoly Artsebarsky is a Soviet-Ukrainian cosmonaut best known for commanding a long-duration mission aboard the Mir space station in 1991.
E1981363 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: Anatoly Artsebarsky | Statement: [Project Juno mission to Mir, crewMember, Anatoly Artsebarsky]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Anatoly Artsebarsky
Triple: [Project Juno mission to Mir, crewMember, Anatoly Artsebarsky]
Generated description
Anatoly Artsebarsky is a Soviet-Ukrainian cosmonaut best known for commanding a long-duration mission aboard the Mir space station in 1991.

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a2e657136d4819089b0a177b3167ef2 completed June 14, 2026, 8:25 a.m.
NEDg Description generation batch_6a2e75664e48819095987fd4bb25c136 completed June 14, 2026, 9:33 a.m.
NED2 Entity disambiguation (via description) batch_6a2e761b73e08190992378beb214bc47 completed June 14, 2026, 9:36 a.m.
Created at: April 10, 2026, 5:37 a.m.