Triple
T33660538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankine cycle |
E862337
|
entity |
| Predicate | hasEnergyConsumption |
P7394
|
FINISHED |
| Object | pump work |
—
|
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: pump work | Statement: [Rankine cycle, hasEnergyConsumption, pump work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyConsumption Context triple: [Rankine cycle, hasEnergyConsumption, pump work]
-
A.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
B.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
C.
energyUse
chosen
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
D.
powerConsumptionWatts
Indicates the amount of electrical power an entity uses, measured in watts, during its operation.
-
E.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:42 a.m.