Triple
T25933475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD Radeon Technologies Group |
E653489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subsidiary organization of AMD |
C16054
|
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: subsidiary organization of AMD Context triple: [AMD Radeon Technologies Group, instanceOf, subsidiary organization of AMD]
-
A.
Intel subsidiary
An Intel subsidiary is a legally distinct company that is majority-owned and controlled by Intel Corporation to support its strategic, operational, or market objectives.
-
B.
subordinate organization
chosen
A subordinate organization is an entity that operates under the authority, control, or oversight of a higher-level organization, carrying out specific functions or responsibilities delegated to it.
-
C.
semiconductor company division
A semiconductor company division is an organizational unit within a semiconductor firm responsible for specific product lines, technologies, or market segments, managing everything from design and development to marketing and support for its assigned portfolio.
-
D.
Fujitsu subsidiary
A Fujitsu subsidiary is a company that is owned or controlled by Fujitsu Limited and operates as part of its broader corporate group, often focusing on specific markets, technologies, or services.
-
E.
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.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:37 a.m.