Triple
T15944234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brayton cycle |
E386643
|
entity |
| Predicate | energyInput |
P58869
|
FINISHED |
| Object | heat addition at constant pressure |
—
|
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: heat addition at constant pressure | Statement: [Brayton cycle, energyInput, heat addition at constant pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyInput Context triple: [Brayton cycle, energyInput, heat addition at constant pressure]
-
A.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
B.
energyContribution
chosen
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
C.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
D.
energyPotential
Indicates a relationship where one entity possesses or confers the capacity to perform work or cause change (potential energy) relative to another entity or state.
-
E.
usesEnergyConversion
Indicates that an entity performs or involves a process where one form of energy is transformed into another to achieve a function or outcome.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.