Triple

T13375084
Position Surface form Disambiguated ID Type / Status
Subject STS-30 E319162 entity
Predicate followedBy P78 FINISHED
Object STS-28 E559636 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-28 | Statement: [STS-30, followedBy, STS-28]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: STS-28
Context triple: [STS-30, followedBy, STS-28]
  • A. STS-28 chosen
    STS-28 was a 1989 NASA Space Shuttle Columbia mission that deployed a classified Department of Defense payload in low Earth orbit.
  • B. STS-29
    STS-29 was a 1989 NASA Space Shuttle Discovery mission that deployed a Tracking and Data Relay Satellite and conducted various scientific experiments in low Earth orbit.
  • C. STS-27
    STS-27 was a 1988 NASA Space Shuttle Atlantis mission primarily dedicated to a classified Department of Defense payload.
  • D. STS-58
    STS-58 was a 1993 NASA Space Shuttle Columbia mission focused on life sciences research, particularly the effects of spaceflight on the human body.
  • E. STS-31
    STS-31 was a 1990 NASA Space Shuttle Discovery mission best known for deploying the Hubble Space Telescope into low Earth orbit.
  • 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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dadcda64a48190b53243a763cd175b completed April 11, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd3cf863fc81908723f7f6b3d45510 completed May 8, 2026, 1:31 a.m.
Created at: April 9, 2026, 9:33 p.m.