Triple
T29870478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Interactive Entertainment |
E758582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Sony |
C8831
|
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: division of Sony Context triple: [Sony Interactive Entertainment, instanceOf, division of Sony]
-
A.
Sony division
chosen
A Sony division is an organizational unit within Sony Corporation responsible for a specific business area, product line, or regional market, operating with its own management, strategy, and performance goals.
-
B.
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.
-
C.
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.
-
D.
division of The Walt Disney Company
A division of The Walt Disney Company is an organizational unit within the corporation responsible for managing a specific line of business, brand portfolio, or operational function under Disney’s overall corporate structure.
-
E.
division of Electronic Arts
A division of Electronic Arts is an organizational unit within the company responsible for specific functions such as game development, publishing, or support services under the broader EA 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:53 p.m.