Triple
T35833295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Jobs' return to Apple |
E1035859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate turnaround event |
C64222
|
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: corporate turnaround event Context triple: [Steve Jobs' return to Apple, instanceOf, corporate turnaround event]
-
A.
corporate restructuring strategy
A corporate restructuring strategy is a comprehensive plan that realigns a company’s organizational structure, operations, and assets to improve efficiency, financial performance, and long-term competitiveness.
-
B.
corporate spin-off
A corporate spin-off is the creation of an independent company by separating part of a parent corporation’s operations, assets, or divisions into a new, standalone entity, typically by distributing shares to existing shareholders.
-
C.
corporate control struggle
A corporate control struggle is a conflict among stakeholders, such as executives, board members, or shareholders, competing to influence or determine the strategic direction and decision-making authority of a company.
-
D.
corporate function
A corporate function is a specialized organizational unit or role responsible for carrying out a distinct set of activities (such as finance, marketing, or human resources) that support and enable a company’s overall strategy and operations.
-
E.
corporate governance reform
Corporate governance reform is the process of changing rules, structures, and practices that direct and control corporations to improve accountability, transparency, and alignment with stakeholder interests.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.