Triple
T11962006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro AG |
E284690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational wholesale company |
C12056
|
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: multinational wholesale company Context triple: [Metro AG, instanceOf, multinational wholesale company]
-
A.
multinational retail corporation
A multinational retail corporation is a large company that operates chains of stores or online retail platforms in multiple countries, selling a wide range of consumer goods and services under a unified brand and management structure.
-
B.
wholesale distribution company
chosen
A wholesale distribution company purchases goods in large quantities from manufacturers or suppliers and resells them in bulk to retailers, businesses, or other intermediaries, typically without selling directly to end consumers.
-
C.
multinational chemical company
A multinational chemical company is a large, globally operating enterprise that researches, manufactures, and distributes a wide range of chemical products and materials across multiple industries and countries.
-
D.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
-
E.
merchandising company
A merchandising company is a business that purchases finished goods from suppliers and resells them to customers for a profit, without significantly altering the products.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.