Triple
T1598430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51L |
E34336
|
entity |
| Predicate | timeAfterLiftoffOfBreakup |
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: [STS-51L, timeAfterLiftoffOfBreakup, 73 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAfterLiftoffOfBreakup Context triple: [STS-51L, timeAfterLiftoffOfBreakup, 73 seconds]
-
A.
timeAfterLiftoffAtBreakup
chosen
Indicates the elapsed time since liftoff at the moment when a breakup event (such as vehicle disintegration or structural failure) occurs.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a916d413f08190a4e137e5ed262e25 |
completed | March 5, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69a907bfb39c8190a31e0be14d3d52e6 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.