Triple
T22660045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-28 |
E559636
|
entity |
| Predicate | orbiterFlightNumber |
P38973
|
FINISHED |
| Object | Columbia flight 8 |
—
|
NE NERFINISHED |
How this triple was built (3 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: Columbia flight 8 | Statement: [STS-28, orbiterFlightNumber, Columbia flight 8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Columbia flight 8 Context triple: [STS-28, orbiterFlightNumber, Columbia flight 8]
-
A.
Columbia flight 3
Columbia flight 3 was the third orbital mission of NASA’s Space Shuttle program, flown by the Space Shuttle Columbia in 1982 to test the shuttle’s systems and capabilities.
-
B.
Columbia disaster
The Columbia disaster was the 2003 Space Shuttle tragedy in which the orbiter Columbia broke apart during reentry, killing all seven astronauts aboard and leading to major changes in NASA’s human spaceflight program.
-
C.
Braniff Flight 542
Braniff Flight 542 was a 1959 Braniff Airways domestic passenger flight that broke up in midair near Buffalo, Texas, killing all aboard and becoming one of the early fatal accidents involving the Lockheed L-188 Electra.
-
D.
Space Shuttle Challenger disaster
The Space Shuttle Challenger disaster was the 1986 launch failure in which NASA’s Space Shuttle Challenger broke apart shortly after liftoff, killing all seven crew members and prompting major reforms in the U.S. space program.
-
E.
TWA Flight 741
TWA Flight 741 was a Trans World Airlines international passenger flight that became widely known after being hijacked and diverted during the 1970 Dawson's Field hijackings.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Columbia flight 8 Target entity description: Columbia flight 8 was the eighth spaceflight of the Space Shuttle orbiter Columbia, a classified Department of Defense mission flown as STS-28 in 1989.
-
A.
Columbia flight 3
Columbia flight 3 was the third orbital mission of NASA’s Space Shuttle program, flown by the Space Shuttle Columbia in 1982 to test the shuttle’s systems and capabilities.
-
B.
Columbia disaster
The Columbia disaster was the 2003 Space Shuttle tragedy in which the orbiter Columbia broke apart during reentry, killing all seven astronauts aboard and leading to major changes in NASA’s human spaceflight program.
-
C.
Braniff Flight 542
Braniff Flight 542 was a 1959 Braniff Airways domestic passenger flight that broke up in midair near Buffalo, Texas, killing all aboard and becoming one of the early fatal accidents involving the Lockheed L-188 Electra.
-
D.
Space Shuttle Challenger disaster
The Space Shuttle Challenger disaster was the 1986 launch failure in which NASA’s Space Shuttle Challenger broke apart shortly after liftoff, killing all seven crew members and prompting major reforms in the U.S. space program.
-
E.
TWA Flight 741
TWA Flight 741 was a Trans World Airlines international passenger flight that became widely known after being hijacked and diverted during the 1970 Dawson's Field hijackings.
- F. None of above. chosen
Provenance (2 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 3:07 p.m.