Triple
T36687089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspiro |
E905844
|
entity |
| Predicate | energySavingMeasure |
P27882
|
FINISHED |
| Object | lightweight design |
—
|
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: lightweight design | Statement: [Inspiro, energySavingMeasure, lightweight design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySavingMeasure Context triple: [Inspiro, energySavingMeasure, lightweight design]
-
A.
energyEfficiencyFeature
chosen
Indicates that an entity has a design, technology, or characteristic specifically intended to reduce energy consumption or improve energy performance.
-
B.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
C.
energyImplication
Indicates that one state, action, or condition entails or leads to a particular outcome in terms of energy use, transfer, or impact.
-
D.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
E.
energyStrategy
Indicates a relationship where an entity adopts, follows, or is characterized by a particular plan or approach for producing, managing, or using energy.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7c4c184819093320c638d454c7f |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.