Triple
T30145051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAN Bus |
E766231
|
entity |
| Predicate | usesPowertrain |
P45712
|
FINISHED |
| Object | diesel engines |
—
|
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: diesel engines | Statement: [MAN Bus, usesPowertrain, diesel engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowertrain Context triple: [MAN Bus, usesPowertrain, diesel engines]
-
A.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
-
B.
powertrainCategory
Indicates the classification of a vehicle’s powertrain based on how it delivers propulsion (e.g., internal combustion, hybrid, electric).
-
C.
primaryPowertrain
chosen
Indicates the main powertrain system that primarily provides propulsion or drive power for a vehicle or machine.
-
D.
powertrainProduction
Indicates a relationship where an entity is involved in the manufacturing or assembly of a vehicle’s powertrain components.
-
E.
powertrainOutput
Indicates the relationship where a powertrain produces or delivers mechanical or electrical output (such as torque, power, or motion) to another component or system.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 7:18 p.m.