Triple
T35741091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT 530 |
E1033034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | General Motors truck platform |
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: General Motors truck platform Context triple: [GMT 530, instanceOf, General Motors truck platform]
-
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.
Ford vehicle platform
A Ford vehicle platform is a shared engineering and structural foundation used across multiple Ford models to standardize components, reduce costs, and streamline design and production.
-
C.
General Motors engine
A General Motors engine is a powertrain component designed and manufactured by General Motors to convert fuel or electrical energy into mechanical power for propelling GM vehicles and operating their auxiliary systems.
-
D.
Toyota vehicle platform
A Toyota vehicle platform is a shared engineering and structural foundation used across multiple Toyota and Lexus models to standardize components, improve manufacturing efficiency, and enhance performance and safety.
-
E.
Chevrolet brand
Chevrolet brand is a globally recognized American automotive marque known for producing a wide range of vehicles—from affordable compact cars and family SUVs to performance sports cars and trucks—emphasizing practicality, value, and broad market appeal.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.