Triple
T14915869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors global engineering network |
E371380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit of General Motors |
C34589
|
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: organizational unit of General Motors Context triple: [General Motors global engineering network, instanceOf, organizational unit of General Motors]
-
A.
Ford Motor Company division
A Ford Motor Company division is an organizational unit within Ford responsible for specific product lines, markets, or business functions, operating under the broader corporate structure and strategy of the company.
-
B.
General Motors factory
A General Motors factory is a large-scale automotive manufacturing facility where GM designs, assembles, and tests vehicles and related components using industrial machinery, robotics, and human labor.
-
C.
Stellantis organizational unit
A Stellantis organizational unit is a defined structural entity within Stellantis responsible for specific functions, regions, brands, or business activities, operating under the company’s governance, processes, and strategic objectives.
-
D.
Opel brand division
The Opel brand division represents the organizational unit within an automotive company responsible for the design, production, marketing, and sales of vehicles under the Opel marque.
-
E.
General Motors platform
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.
- F. None of above. chosen
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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:31 a.m.