Triple
T6079813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-58 |
E135492
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | STS-61 |
E34755
|
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-61 | Statement: [STS-58, followedBy, STS-61]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STS-61 Context triple: [STS-58, followedBy, STS-61]
-
A.
STS-61
chosen
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.
-
B.
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.
-
C.
STS-66
STS-66 was a 1994 Space Shuttle Atlantis mission focused on studying Earth's atmosphere and climate using the ATLAS-3 payload and related experiments.
-
D.
STS-6
STS-6 was the maiden flight of the Space Shuttle Challenger, a 1983 NASA mission that deployed the first Tracking and Data Relay Satellite (TDRS-1).
-
E.
STS-51-I
STS-51-I was a 1985 NASA Space Shuttle Discovery mission focused on deploying and repairing communications satellites in 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1358175608190b06bbbc72c6d92c2 |
completed | March 23, 2026, 12:43 p.m. |
Created at: March 22, 2026, 4:11 p.m.