Triple
T4087660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algorand blockchain protocol |
E87625
|
entity |
| Predicate | energyConsumptionProfile |
P7394
|
FINISHED |
| Object | low energy usage |
—
|
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: low energy usage | Statement: [Algorand blockchain protocol, energyConsumptionProfile, low energy usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyConsumptionProfile Context triple: [Algorand blockchain protocol, energyConsumptionProfile, low energy usage]
-
A.
energyUse
chosen
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
B.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
C.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
D.
designEnergy
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
-
E.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca899008190b5ada98bdb79639f |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.