Triple
T27343453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery (OV-103) |
E684169
|
entity |
| Predicate | returnToFlightMissionAfterColumbia |
P21491
|
FINISHED |
| Object | STS-114 |
—
|
NE NERFINISHED |
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-114 | Statement: [Discovery (OV-103), returnToFlightMissionAfterColumbia, STS-114]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnToFlightMissionAfterColumbia Context triple: [Discovery (OV-103), returnToFlightMissionAfterColumbia, STS-114]
-
A.
returnToFlightMission
chosen
Indicates a mission whose purpose is to resume or validate flight operations after they have been suspended or interrupted.
-
B.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
-
C.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
D.
Columbia disaster
Indicates the relationship of being involved in, affected by, or causally connected to the Space Shuttle Columbia disaster event.
-
E.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
- F. None of above.
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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:44 a.m.