Triple
T32234915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulliner |
E823441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive personalization division |
C28111
|
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: automotive personalization division Context triple: [Mulliner, instanceOf, automotive personalization division]
-
A.
automotive customization division
chosen
The automotive customization division is a specialized unit responsible for designing, modifying, and personalizing vehicles to meet specific aesthetic, performance, and functional requirements beyond standard factory configurations.
-
B.
automotive sub-brand
An automotive sub-brand is a distinct product line or division created by a parent car manufacturer to target specific market segments, brand images, or technologies while leveraging the parent company’s resources and reputation.
-
C.
custom automobile
A custom automobile is a uniquely modified or specially built vehicle tailored to an owner's specific aesthetic, performance, and functional preferences beyond standard factory specifications.
-
D.
vehicle styling
Vehicle styling is the conceptual class that encompasses the aesthetic design, form, and visual character of vehicles, including their proportions, surfaces, details, and overall emotional impression.
-
E.
automotive experience center
An automotive experience center is a dedicated venue where visitors can explore, interact with, and test-drive vehicles while engaging with a brand’s technology, services, and lifestyle offerings in an immersive environment.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.