Triple
T12452679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unilever Sustainable Living Plan |
E297569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-term business strategy |
C7550
|
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: long-term business strategy Context triple: [Unilever Sustainable Living Plan, instanceOf, long-term business strategy]
-
A.
long-term plan
chosen
A long-term plan is a structured, forward-looking strategy that outlines major goals and the sequence of actions needed to achieve them over an extended period of time.
-
B.
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.
-
C.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
D.
regional strategy
A regional strategy is a coordinated plan that aligns resources, initiatives, and policies to achieve specific objectives within a defined geographic area, considering its unique economic, cultural, and competitive context.
-
E.
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.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.