Triple
T33187817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mireo |
E849519
|
entity |
| Predicate | energySavingComparedToOlderStock |
P27882
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mireo, energySavingComparedToOlderStock, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySavingComparedToOlderStock Context triple: [Mireo, energySavingComparedToOlderStock, yes]
-
A.
typicalEfficiencyComparedToPredecessor
Indicates how the usual or average efficiency of something compares to that of its predecessor.
-
B.
energyEfficiencyFeature
chosen
Indicates that an entity has a design, technology, or characteristic specifically intended to reduce energy consumption or improve energy performance.
-
C.
energyBeforeUpgrade
Indicates the amount or state of energy associated with an entity prior to a specified upgrade or improvement action.
-
D.
energyEfficiencyClass
Indicates the energy efficiency rating category assigned to an item, typically reflecting how efficiently it uses or conserves energy relative to defined standards.
-
E.
energyRecoveryRegulation
Indicates a regulation that governs how energy is recovered, managed, or reused within a system or process.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:29 a.m.