Triple
T26819443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempesto |
E675204
|
entity |
| Predicate | accelerationStyle |
P161507
|
FINISHED |
| Object | multiple forward and backward launches |
—
|
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: multiple forward and backward launches | Statement: [Tempesto, accelerationStyle, multiple forward and backward launches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accelerationStyle Context triple: [Tempesto, accelerationStyle, multiple forward and backward launches]
-
A.
accelerationElement
Indicates that one entity is an element or component contributing to the acceleration of another entity or process.
-
B.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
C.
optimizationStyle
Indicates the particular method or approach used to optimize a process, system, or solution.
-
D.
accelerationDistance
Indicates the distance over which an object accelerates (i.e., the spatial extent during which its velocity increases).
-
E.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61a886f148190b0de71e54e905958 |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 4:54 a.m.