Triple
T310181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Challenger disaster |
E6388
|
entity |
| Predicate | timeAfterLiftoffAtBreakup |
P10667
|
FINISHED |
| Object | 73 seconds |
—
|
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: 73 seconds | Statement: [Space Shuttle Challenger disaster, timeAfterLiftoffAtBreakup, 73 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAfterLiftoffAtBreakup Context triple: [Space Shuttle Challenger disaster, timeAfterLiftoffAtBreakup, 73 seconds]
-
A.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
E.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.