Triple

T4545071
Position Surface form Disambiguated ID Type / Status
Subject OV-103 E110025 entity
Predicate notableMission P68 FINISHED
Object STS-31 E46722 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: STS-31 | Statement: [OV-103, notableMission, STS-31]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: STS-31
Context triple: [OV-103, notableMission, STS-31]
  • A. STS-31 chosen
    STS-31 was a 1990 NASA Space Shuttle Discovery mission best known for deploying the Hubble Space Telescope into low Earth orbit.
  • B. STS-30
    STS-30 was a 1989 NASA Space Shuttle Atlantis mission notable for deploying the Magellan spacecraft to Venus.
  • C. STS-51-C
    STS-51-C was a 1985 classified U.S. Department of Defense Space Shuttle Discovery mission notable for being the first spaceflight of astronaut Ellison Onizuka.
  • D. STS-51-L
    STS-51-L was the ill-fated 1986 Space Shuttle Challenger mission that ended in disaster shortly after launch, resulting in the loss of all seven crew members.
  • E. STS-41C
    STS-41C was a 1984 NASA Space Shuttle Challenger mission notable for successfully repairing the Solar Maximum Mission satellite during the first on-orbit satellite repair operation.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd4412524c8190be5bcc9ddee91848 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57d62a8481909d5d803a582c76a1 completed March 20, 2026, 2:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfa1681708190ae4dc66e8734e5a1 completed March 21, 2026, 1:53 a.m.
Created at: March 20, 2026, 1:05 p.m.