Triple
T36561252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Kushner |
E901843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate turnaround specialist |
C14866
|
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 specialist Context triple: [Brian Kushner, instanceOf, corporate turnaround specialist]
-
A.
corporate turnaround event
A corporate turnaround event is a significant, often time-bound intervention in which a struggling company implements strategic, financial, and operational changes to restore stability, profitability, and long-term viability.
-
B.
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.
-
C.
business transformation company
A business transformation company is an organization that helps other businesses fundamentally improve their performance by redesigning strategies, processes, technologies, and organizational structures to adapt to changing markets and achieve long-term growth.
-
D.
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.
-
E.
management consultant
chosen
A management consultant is a professional who analyzes organizations’ operations and strategies to provide expert advice and solutions that improve performance, efficiency, and overall business outcomes.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.