Triple
T27343450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery (OV-103) |
E684169
|
entity |
| Predicate | returnToFlightAfter |
P70776
|
FINISHED |
| Object | Challenger disaster |
—
|
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: Challenger disaster | Statement: [Discovery (OV-103), returnToFlightAfter, Challenger disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnToFlightAfter Context triple: [Discovery (OV-103), returnToFlightAfter, Challenger disaster]
-
A.
returnToFlightMission
Indicates a mission whose purpose is to resume or validate flight operations after they have been suspended or interrupted.
-
B.
returnedToFlightStatus
chosen
Indicates that an entity previously grounded, inactive, or suspended has been restored to an approved or operational flight status.
-
C.
reflightOf
Indicates that one flight is a re-scheduled, repeated, or follow-up instance of another original flight.
-
D.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
-
E.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:44 a.m.