Triple
T35752181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | enhanced Energy Recovery System |
E1033346
|
entity |
| Predicate | harvestsEnergyFrom |
P93282
|
FINISHED |
| Object | braking phases |
—
|
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: braking phases | Statement: [enhanced Energy Recovery System, harvestsEnergyFrom, braking phases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvestsEnergyFrom Context triple: [enhanced Energy Recovery System, harvestsEnergyFrom, braking phases]
-
A.
usesEnergyFrom
chosen
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
B.
derivesPowerFrom
Indicates that one entity obtains or is granted its power, authority, or energy as a result of another entity.
-
C.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
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.
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a197aee48190bbd69f670a3f7721 |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.