Triple
T7628637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kia Georgia, Inc. |
E172701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kia Corporation subsidiary |
C22621
|
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: Kia Corporation subsidiary Context triple: [Kia Georgia, Inc., instanceOf, Kia Corporation subsidiary]
-
A.
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.
-
B.
South Korean company
A South Korean company is a business entity legally registered and operating in South Korea, typically structured under its corporate laws and engaged in commercial, industrial, or service activities within domestic and global markets.
-
C.
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.
-
D.
Sony Group subsidiary
A Sony Group subsidiary is a company that is majority-owned or otherwise controlled by Sony Group Corporation, operating under its corporate umbrella while focusing on specific business areas such as electronics, entertainment, or financial services.
-
E.
Samsung division
A Samsung division is an organizational unit within Samsung Group responsible for managing specific product lines, services, or business functions under the broader corporate strategy.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.