Triple
T13227930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | smart EQ fortwo |
E314928
|
entity |
| Predicate | energyRecovery |
P44376
|
FINISHED |
| Object | regenerative braking |
—
|
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: regenerative braking | Statement: [smart EQ fortwo, energyRecovery, regenerative braking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRecovery Context triple: [smart EQ fortwo, energyRecovery, regenerative braking]
-
A.
energyRecoverySystem
chosen
Indicates that an entity is equipped with or utilizes a system designed to recover and reuse energy that would otherwise be lost.
-
B.
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.
-
C.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
-
D.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
E.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.