Triple
T12452623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foods & Refreshment |
E297567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Unilever business division |
C31476
|
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: Unilever business division Context triple: [Foods & Refreshment, instanceOf, Unilever business division]
-
A.
division of L'Oréal
A division of L'Oréal is an organizational unit within the company responsible for a specific portfolio of brands, markets, or product categories, operating with its own strategy, management, and resources under the broader L'Oréal corporate structure.
-
B.
beauty conglomerate
A beauty conglomerate is a large parent company that owns, manages, and coordinates multiple beauty and personal care brands across diverse markets and product categories.
-
C.
Newell Brands business segment
The Newell Brands business segment is a conceptual grouping of the company’s related product lines and operations organized for strategic management, financial reporting, and performance evaluation within the broader Newell Brands portfolio.
-
D.
Mercedes-Benz division
A Mercedes-Benz division is an organizational unit within the Mercedes-Benz company responsible for a specific product line, market segment, or operational function, such as passenger cars, commercial vehicles, or financial services.
-
E.
Opel brand division
The Opel brand division represents the organizational unit within an automotive company responsible for the design, production, marketing, and sales of vehicles under the Opel marque.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.