Triple

T32820606
Position Surface form Disambiguated ID Type / Status
Subject STS-31 Hubble deployment E839423 entity
Predicate relatedTelescope P41860 FINISHED
Object Hubble Space Telescope E7921 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: Hubble Space Telescope | Statement: [STS-31 Hubble deployment, relatedTelescope, Hubble Space Telescope]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedTelescope
Context triple: [STS-31 Hubble deployment, relatedTelescope, Hubble Space Telescope]
  • A. relatedAstronomicalObject
    Indicates that one astronomical object has a specified relationship or association with another astronomical object.
  • B. neighboringTelescopes
    Indicates that two telescopes are located close to each other such that they are considered neighbors, typically within the same observing site or adjacent positions.
  • C. relatedConstellation
    Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
  • D. hasSisterTelescope
    Indicates that one telescope is considered a sister telescope to another, typically due to a close partnership, shared design, or coordinated observational role.
  • E. telescopeAssociation chosen
    Indicates an association or linkage between a telescope and another entity, such as an instrument, observation, project, or location, showing that they are functionally or contextually related.
  • F. None of above.

Provenance (4 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_69f3493df9008190a8f5d843dcd77704 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_6a037cad051c8190b28b354b89208574 completed May 12, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a34c66e655c8190b9ad180507f6067f completed June 19, 2026, 4:32 a.m.
PD Predicate disambiguation batch_6a0379f0cbe481909b4b8fc6cbe297f0 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:15 a.m.