Triple
T28990894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | energyRecoveryType |
P5332
|
FINISHED |
| Object | kinetic energy recovery |
—
|
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: kinetic energy recovery | Statement: [Ferrari V6 turbo hybrid, energyRecoveryType, kinetic energy recovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRecoveryType Context triple: [Ferrari V6 turbo hybrid, energyRecoveryType, kinetic energy recovery]
-
A.
energyRecoverySystem
Indicates that an entity is equipped with or utilizes a system designed to recover and reuse energy that would otherwise be lost.
-
B.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
C.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
D.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
-
E.
energyHub
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 9:25 a.m.