Triple
T24124146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baojun 200 series |
E597745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crossover SUV series |
C3082
|
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: crossover SUV series Context triple: [Baojun 200 series, instanceOf, crossover SUV series]
-
A.
compact crossover SUV
chosen
A compact crossover SUV is a small, car-based sport utility vehicle that combines the higher seating position and versatility of an SUV with the maneuverability, fuel efficiency, and ride comfort of a compact car.
-
B.
subcompact crossover SUV
A subcompact crossover SUV is a small, car-based sport utility vehicle that combines the higher seating position and versatility of an SUV with the compact size and maneuverability of a subcompact car.
-
C.
crossover-style liftback
A crossover-style liftback is a vehicle that blends the higher ride height and rugged styling of a crossover with the sloping rear roofline and large, hinged rear hatch of a liftback for added practicality and a sporty profile.
-
D.
luxury midsize SUV
A luxury midsize SUV is a premium sport utility vehicle that combines upscale materials, advanced technology, and refined performance with spacious seating and versatile cargo capacity in a mid-sized footprint.
-
E.
sport utility vehicle
A sport utility vehicle is a versatile passenger vehicle that combines elements of on-road cars and off-road trucks, typically offering higher ground clearance, spacious interiors, and optional all-wheel or four-wheel drive for varied driving conditions.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:06 p.m.