Triple
T6058943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz USA |
E134983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz division |
C19844
|
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: Mercedes-Benz division Context triple: [Mercedes-Benz USA, instanceOf, Mercedes-Benz division]
-
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.
BMW vehicle line
A BMW vehicle line is a distinct series of BMW-branded automobiles that share a common platform, design language, and performance characteristics, targeting a specific market segment or customer need.
-
C.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
-
D.
BMW brand extension
BMW brand extension refers to the strategic use of the BMW brand name to launch new products or services beyond its core automobile offerings, leveraging existing brand equity to enter related or new market segments.
-
E.
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.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.