Triple
T22236595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 139 |
E549607
|
entity |
| Predicate | brakingEnergyUse |
P44376
|
FINISHED |
| Object | regenerative to flywheel |
—
|
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 to flywheel | Statement: [British Rail Class 139, brakingEnergyUse, regenerative to flywheel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakingEnergyUse Context triple: [British Rail Class 139, brakingEnergyUse, regenerative to flywheel]
-
A.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
B.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
C.
energyRecoverySystem
chosen
Indicates that an entity is equipped with or utilizes a system designed to recover and reuse energy that would otherwise be lost.
-
D.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
E.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf7b1d8819091087dcfdb2e967c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.