Triple
T310189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Challenger disaster |
E6388
|
entity |
| Predicate | shuttleProgramFlightPauseDuration |
P7618
|
FINISHED |
| Object | approximately 32 months |
—
|
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: approximately 32 months | Statement: [Space Shuttle Challenger disaster, shuttleProgramFlightPauseDuration, approximately 32 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shuttleProgramFlightPauseDuration Context triple: [Space Shuttle Challenger disaster, shuttleProgramFlightPauseDuration, approximately 32 months]
-
A.
flightDuration
Indicates the length of time that a specific flight takes from departure to arrival.
-
B.
pilotTourLength
Indicates the duration or total length of a pilot’s tour, assignment, or rotation.
-
C.
departurePilot
Indicates that a pilot is responsible for operating or commanding the departing flight or vehicle.
-
D.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
runwayLength
Indicates the length of a runway associated with an airport or airfield.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.