Triple

T36293659
Position Surface form Disambiguated ID Type / Status
Subject Hubble Space Telescope computer E893299 entity
Predicate wasUpgradedDuring P92626 FINISHED
Object Servicing Mission 3A NE NERFINISHED

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: Servicing Mission 3A | Statement: [Hubble Space Telescope computer, wasUpgradedDuring, Servicing Mission 3A]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasUpgradedDuring
Context triple: [Hubble Space Telescope computer, wasUpgradedDuring, Servicing Mission 3A]
  • A. wasUpgradedFor
    Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
  • B. underwentUpgradeAfter
    Indicates that one entity experienced an upgrade or improvement at some point after another specified event or time associated with a second entity.
  • C. underwentUpgrade chosen
    Indicates that an entity has experienced an improvement or enhancement process that changed it to a newer or more advanced state.
  • D. upgradedBy
    Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
  • E. hasUpgrade
    Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
  • 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_69f76e4a61f0819084a2b68dbbb4efc6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba6d06f48190a71b5a2f19e2232f completed May 3, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.