Triple
T26389708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Powertrains (Honda-based) |
E663377
|
entity |
| Predicate | energyRecoveryComponents |
P44376
|
FINISHED |
| Object | MGU-K |
—
|
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: MGU-K | Statement: [Red Bull Powertrains (Honda-based), energyRecoveryComponents, MGU-K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRecoveryComponents Context triple: [Red Bull Powertrains (Honda-based), energyRecoveryComponents, MGU-K]
-
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.
energyHub
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
-
C.
powerConversionSystem
Indicates a system that transforms electrical power from one form, level, or source into another to meet specific usage or distribution requirements.
-
D.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
-
E.
usedFuelCells
Indicates that an entity employed fuel cells as an energy source or power component in its operation or design.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 11:24 p.m.