Triple
T34422896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALP family of locomotives |
E883595
|
entity |
| Predicate | braking |
P4166
|
FINISHED |
| Object | dynamic braking |
—
|
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: dynamic braking | Statement: [ALP family of locomotives, braking, dynamic braking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: braking Context triple: [ALP family of locomotives, braking, dynamic braking]
-
A.
hasBraking
Indicates that an entity possesses or is equipped with a braking capability or braking system.
-
B.
brakeFeature
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
C.
brakeApplication
Indicates that a braking action is being applied to slow down or stop an entity.
-
D.
brakeType
chosen
Indicates the specific kind or system of brakes associated with an entity.
-
E.
hasBrakingRole
Indicates that an entity participates in a braking process by fulfilling a specific braking-related function or responsibility.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.