Triple
T34602467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 378 |
E888502
|
entity |
| Predicate | brakeControl |
P109345
|
FINISHED |
| Object | regenerative braking capability |
—
|
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 braking capability | Statement: [British Rail Class 378, brakeControl, regenerative braking capability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakeControl Context triple: [British Rail Class 378, brakeControl, regenerative braking capability]
-
A.
brakeFeature
chosen
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
B.
brakeApplication
Indicates that a braking action is being applied to slow down or stop an entity.
-
C.
brakeType
Indicates the specific kind or system of brakes associated with an entity.
-
D.
hasBraking
Indicates that an entity possesses or is equipped with a braking capability or braking system.
-
E.
brakeDemand
Indicates that an entity is requesting or applying a braking action, specifying the needed braking force or intensity.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.