Triple
T30360536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi A3 e-tron |
E772270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plug-in hybrid automobile |
C13747
|
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: plug-in hybrid automobile Context triple: [Audi A3 e-tron, instanceOf, plug-in hybrid automobile]
-
A.
plug-in hybrid electric vehicle
chosen
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.
-
B.
gasoline-electric hybrid system
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.
-
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.
electrified vehicle
An electrified vehicle is a mode of transportation that uses electricity, either fully or in combination with conventional fuels, to power its propulsion system.
-
E.
high-performance electric crossover
A high-performance electric crossover is a sporty, battery-powered vehicle that blends SUV practicality with car-like handling and rapid acceleration.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:57 p.m.