Triple
T2978090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula One |
E80445
|
entity |
| Predicate | energyRecoverySystem |
P44376
|
FINISHED |
| Object | hybrid power unit with ERS |
—
|
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: hybrid power unit with ERS | Statement: [Formula One, energyRecoverySystem, hybrid power unit with ERS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRecoverySystem Context triple: [Formula One, energyRecoverySystem, hybrid power unit with ERS]
-
A.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
B.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
C.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
D.
emitsMoreEnergyThanItReceives
Indicates that the subject releases a greater amount of energy than it takes in from its surroundings or inputs.
-
E.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.