Triple
T32608680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohner-Porsche Mixte Hybrid |
E833593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | series hybrid vehicle |
C13162
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: series hybrid vehicle Context triple: [Lohner-Porsche Mixte Hybrid, instanceOf, series hybrid vehicle]
-
A.
hybrid bus
A hybrid bus is a public transport vehicle that combines an internal combustion engine with an electric propulsion system to improve fuel efficiency and reduce emissions.
-
B.
plug-in hybrid electric vehicle
A plug-in hybrid electric vehicle is a car that combines an internal combustion engine with an electric motor and a rechargeable battery that can be charged from an external power source, allowing it to drive on electric power alone for limited distances before switching to hybrid operation.
-
C.
hybrid powertrain technology
Hybrid powertrain technology integrates an internal combustion engine with one or more electric motors and a battery system to optimize fuel efficiency, reduce emissions, and enhance vehicle performance through intelligent power management.
-
D.
gasoline-electric hybrid system
chosen
A gasoline-electric hybrid system is a powertrain that combines an internal combustion engine with one or more electric motors and a battery to improve fuel efficiency, reduce emissions, and optimize vehicle performance.
-
E.
streamlined passenger car
A streamlined passenger car is a rail vehicle designed with smooth, aerodynamic contours to reduce air resistance and provide efficient, comfortable transport for travelers.
- F. None of above.
Provenance (1 batch)
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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:05 a.m.