Triple
T634093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors commercial vehicle platforms |
E15984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicle platform family |
C2728
|
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: vehicle platform family Context triple: [General Motors commercial vehicle platforms, instanceOf, vehicle platform family]
-
A.
General Motors platform
chosen
A General Motors platform is a shared underlying vehicle architecture, including structural, mechanical, and sometimes electronic components, used across multiple GM models to streamline design, production, and costs.
-
B.
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.
-
C.
luxury vehicle brand
A luxury vehicle brand is a premium automotive marque that emphasizes superior craftsmanship, advanced technology, high performance, and elevated comfort and status to distinguish its vehicles from mainstream offerings.
-
D.
operating system family
An operating system family is a conceptual grouping of related operating systems that share a common architecture, design principles, and core components, often evolving from a shared codebase or lineage.
-
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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.