Triple
T11375662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 802 |
E269459
|
entity |
| Predicate | electricTraction |
P8442
|
FINISHED |
| Object | AC traction motors |
—
|
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: AC traction motors | Statement: [British Rail Class 802, electricTraction, AC traction motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricTraction Context triple: [British Rail Class 802, electricTraction, AC traction motors]
-
A.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
B.
electrification
Indicates the process or state of providing electrical power or converting something to operate using electricity.
-
C.
isElectricRailway
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
-
D.
electricMotorType
chosen
Indicates the specific kind or category of electric motor associated with an entity.
-
E.
railElectrificationIncludes
Indicates that a rail electrification system or project encompasses, covers, or incorporates a specified segment, component, or area of railway infrastructure.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.