Triple
T23674931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz U.S. International |
E584845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz subsidiary |
C37942
|
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 subsidiary Context triple: [Mercedes-Benz U.S. International, instanceOf, Mercedes-Benz subsidiary]
-
A.
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.
-
B.
automotive company subsidiary
chosen
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.
-
C.
Hyundai subsidiary
A Hyundai subsidiary is a company that is owned or controlled by the Hyundai Motor Group or Hyundai Corporation to conduct specific business operations under the broader Hyundai brand.
-
D.
Audi vehicle sub-brand
A distinct line or series of Audi vehicles that shares a common identity, positioning, and design philosophy within the broader Audi brand portfolio.
-
E.
Mercedes-Benz factory
A Mercedes-Benz factory is an industrial facility where Mercedes-Benz vehicles and components are designed, manufactured, assembled, and quality-tested using advanced engineering and automated production systems.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.