Triple
T13180540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Performance with Purpose strategy at PepsiCo |
E313709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate strategy |
C32591
|
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 strategy Context triple: [Performance with Purpose strategy at PepsiCo, instanceOf, corporate strategy]
-
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 board
A corporate board is a group of individuals elected by shareholders to oversee a company's management, set strategic direction, and ensure accountability and compliance with laws and regulations.
-
C.
business growth strategy
A business growth strategy is a structured plan that outlines how a company will expand its revenue, market presence, and capabilities over time through targeted initiatives and resource allocation.
-
D.
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.
-
E.
marketing strategy
A marketing strategy is a comprehensive plan that defines how a business will identify, reach, and persuade its target audience to achieve specific marketing and organizational goals.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.