Triple
T17659778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia (as Holden Captiva 5) |
E440218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive market designation |
C24714
|
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 market designation Context triple: [Australia (as Holden Captiva 5), instanceOf, automotive market designation]
-
A.
automotive market segment
An automotive market segment is a distinct group of consumers or vehicles within the broader car market, defined by shared characteristics such as price range, vehicle type, performance, and intended use.
-
B.
regional automotive market
chosen
A regional automotive market is a geographically defined area in which automotive products and services are bought and sold, shaped by local consumer preferences, economic conditions, regulations, and competitive dynamics.
-
C.
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.
-
D.
automotive brand
An automotive brand is a conceptual entity representing the identity, reputation, and market presence of a manufacturer that designs, produces, and sells motor vehicles under a distinct name and image.
-
E.
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.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 9:40 a.m.