Triple
T9808823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Discovery |
E238217
|
entity |
| Predicate | notableMission |
P68
|
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: [Space Shuttle Discovery, notableMission, STS-26]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STS-26 Context triple: [Space Shuttle Discovery, notableMission, 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-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.
-
C.
STS-67
STS-67 was a 1995 NASA Space Shuttle Endeavour mission focused on ultraviolet astronomy as part of the Astro-2 observatory program.
-
D.
STS-27
STS-27 was a 1988 NASA Space Shuttle Atlantis mission primarily dedicated to a classified Department of Defense payload.
-
E.
STS-56
STS-56 was a 1993 NASA Space Shuttle Discovery mission focused on studying Earth's atmosphere and solar interactions using the ATLAS-2 payload.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb21ef32c8190ab4b09d157798451 |
completed | April 2, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e15435faa881909b1a124f8027deeb |
completed | April 16, 2026, 9:27 p.m. |
Created at: March 30, 2026, 8:29 p.m.