Triple
T955463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M9 electric multiple unit |
E20615
|
entity |
| Predicate | brakeSystem |
P4166
|
FINISHED |
| Object | electro‑pneumatic brakes |
—
|
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: electro‑pneumatic brakes | Statement: [M9 electric multiple unit, brakeSystem, electro‑pneumatic brakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakeSystem Context triple: [M9 electric multiple unit, brakeSystem, electro‑pneumatic brakes]
-
A.
brakeType
chosen
Indicates the specific kind or system of brakes associated with an entity.
-
B.
suspensionType
Indicates the specific kind or configuration of suspension system associated with an entity (e.g., a vehicle or structure).
-
C.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
D.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
E.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3f7a7608190b8a8dd2486654bec |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.