Triple
T16859355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Motor America |
E409867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive company 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: automotive company subsidiary Context triple: [Hyundai Motor America, instanceOf, automotive company subsidiary]
-
A.
automotive sub-brand
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.
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.
-
C.
Kia Corporation subsidiary
A Kia Corporation subsidiary is a legally distinct company that is majority-owned or controlled by Kia Corporation to support its automotive manufacturing, distribution, or related business operations.
-
D.
Toyota brand subline
A Toyota brand subline is a distinct product or model range within the Toyota brand that targets a specific market segment, feature set, or customer need while remaining under the overarching Toyota identity.
-
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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.