Triple

T9808822
Position Surface form Disambiguated ID Type / Status
Subject Space Shuttle Discovery E238217 entity
Predicate missionSTS-31Role P21471 FINISHED
Object Hubble Space Telescope deployment 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: Hubble Space Telescope deployment | Statement: [Space Shuttle Discovery, missionSTS-31Role, Hubble Space Telescope deployment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: missionSTS-31Role
Context triple: [Space Shuttle Discovery, missionSTS-31Role, Hubble Space Telescope deployment]
  • A. spaceShuttleApproachAndLandingTestCrew
    Indicates that the entities form the crew involved in a space shuttle approach and landing test.
  • B. spacelabSeries
    Indicates that one entity is part of, or belongs to, a particular series of Spacelab missions or modules.
  • C. associatedSpaceShuttleAstronauts
    Indicates that there is an association or relevant connection between a given subject and one or more space shuttle astronauts.
  • D. Apollo1Crewmate
    Indicates that one entity is a member of the crew of the Apollo 1 space mission in relation to another entity.
  • E. missionSpecialist chosen
    Indicates that an entity serves in the role of a mission specialist in relation to a particular mission or spaceflight.
  • 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_69ca84defac48190abc1148804f184c1 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb21ef32c8190ab4b09d157798451 completed April 2, 2026, 12:02 a.m.
PD Predicate disambiguation batch_69cd03dd2da881909052fbf29736a773 completed April 1, 2026, 11:39 a.m.
Created at: March 30, 2026, 8:29 p.m.