Triple
T8948589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-121 |
E213285
|
entity |
| Predicate | returnToFlightPhase |
P21491
|
FINISHED |
| Object | post-Columbia Return to Flight |
—
|
LITERAL 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: post-Columbia Return to Flight | Statement: [STS-121, returnToFlightPhase, post-Columbia Return to Flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnToFlightPhase Context triple: [STS-121, returnToFlightPhase, post-Columbia Return to Flight]
-
A.
returnToFlightMission
chosen
Indicates a mission whose purpose is to resume or validate flight operations after they have been suspended or interrupted.
-
B.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
C.
flightPhase
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
D.
testFlightPhase
Indicates the specific phase or stage of a test flight that an aircraft or system is currently in.
-
E.
returnedToFlightStatus
Indicates that an entity previously grounded, inactive, or suspended has been restored to an approved or operational flight status.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6709c7a48190ab503083a1d6a29f |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.