Triple
T35006846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Division of Ford Motor Company |
E1009832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive brand division |
C36853
|
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 brand division Context triple: [Ford Division of Ford Motor Company, instanceOf, automotive brand division]
-
A.
automotive sub-brand
chosen
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.
-
B.
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.
-
C.
automotive company subsidiary
An automotive company subsidiary is a legally distinct company controlled by a larger parent automaker that focuses on specific functions such as manufacturing, design, regional operations, or specialized vehicle brands within the overall corporate structure.
-
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.
Mercedes-Benz division
A Mercedes-Benz division is an organizational unit within the Mercedes-Benz company responsible for a specific product line, market segment, or operational function, such as passenger cars, commercial vehicles, or financial services.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.