Triple
T13070033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G22/G23/G26 |
E329431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BMW model series designation |
C12397
|
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: BMW model series designation Context triple: [G22/G23/G26, instanceOf, BMW model series designation]
-
A.
BMW vehicle line
chosen
A BMW vehicle line is a distinct series of BMW-branded automobiles that share a common platform, design language, and performance characteristics, targeting a specific market segment or customer need.
-
B.
BMW brand extension
BMW brand extension refers to the strategic use of the BMW brand name to launch new products or services beyond its core automobile offerings, leveraging existing brand equity to enter related or new market segments.
-
C.
automobile model
An automobile model is a specific version of a vehicle produced by a manufacturer, defined by a distinct combination of design, features, and specifications that differentiates it from other vehicles in the product lineup.
-
D.
Lexus internal chassis code
A Lexus internal chassis code is a manufacturer-assigned alphanumeric identifier that designates a specific Lexus vehicle platform, generation, and major mechanical configuration for engineering and cataloging purposes.
-
E.
Toyota chassis code
A Toyota chassis code is an alphanumeric identifier used by Toyota to specify a vehicle’s platform, engine type, drivetrain, and generation for classification and parts/reference purposes.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9 p.m.