Triple
T15422188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immelmann turn |
E369407
|
entity |
| Predicate | effectOnEnergy |
P74280
|
FINISHED |
| Object | trades airspeed for altitude |
—
|
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: trades airspeed for altitude | Statement: [Immelmann turn, effectOnEnergy, trades airspeed for altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnEnergy Context triple: [Immelmann turn, effectOnEnergy, trades airspeed for altitude]
-
A.
hasEnergyBalanceEffect
chosen
Indicates that one entity produces an effect on the energy balance or energy regulation of another entity or system.
-
B.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
C.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
D.
energyExchangeAbility
Indicates the capacity of one entity to transfer, share, or convert energy with another entity within a given context.
-
E.
energyLevel
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebe7b1081908e6b9e6e128a8d5d |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.