Triple
T1598465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51L |
E34336
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | STS-26 |
E41067
|
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-26 | Statement: [STS-51L, followedBy, STS-26]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STS-26 Context triple: [STS-51L, followedBy, STS-26]
-
A.
STS-26
chosen
STS-26 was the 1988 NASA Space Shuttle mission that marked the program’s return to flight following the Challenger disaster.
-
B.
STS-76
STS-76 was a 1996 NASA Space Shuttle Atlantis mission notable for delivering astronaut Shannon Lucid to the Russian Mir space station for a long-duration stay.
-
C.
STS-31
STS-31 was a 1990 NASA Space Shuttle Discovery mission best known for deploying the Hubble Space Telescope into low Earth orbit.
-
D.
STS-61
STS-61 was a 1993 NASA Space Shuttle Endeavour mission best known for successfully repairing and upgrading the Hubble Space Telescope during a series of complex spacewalks.
-
E.
STS-61-C
STS-61-C was a 1986 NASA Space Shuttle Columbia mission notable for carrying future U.S. Senator and NASA Administrator Bill Nelson as a payload specialist.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9092f5f148190b987bc943e89e29c |
completed | March 5, 2026, 4:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad797d8c68819093fb2bcae0a08698 |
completed | March 8, 2026, 1:28 p.m. |
Created at: March 4, 2026, 7:27 p.m.