Triple
T7574396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OV-099 |
E179324
|
entity |
| Predicate | notableMission |
P68
|
FINISHED |
| Object | STS-51-B |
E490113
|
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-51-B | Statement: [OV-099, notableMission, STS-51-B]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STS-51-B Context triple: [OV-099, notableMission, STS-51-B]
-
A.
STS-51-B
chosen
STS-51-B was a 1985 NASA Space Shuttle Challenger mission focused on Spacelab scientific research in microgravity.
-
B.
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.
-
C.
STS-51-I
STS-51-I was a 1985 NASA Space Shuttle Discovery mission focused on deploying and repairing communications satellites in Earth orbit.
-
D.
STS-51-F
STS-51-F was a 1985 NASA Space Shuttle Challenger mission notable for its Spacelab 2 scientific payload and an in-flight main engine shutdown that led to the first use of an Abort to Orbit procedure.
-
E.
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.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9162980708190be2a347b2322c09c |
completed | March 29, 2026, 12:08 p.m. |
Created at: March 27, 2026, 3:51 p.m.