Triple
T15743942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Department Stores Company |
E381670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department store holding company |
C13306
|
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: department store holding company Context triple: [May Department Stores Company, instanceOf, department store holding company]
-
A.
department store
A department store is a large retail establishment that offers a wide variety of goods, such as clothing, home furnishings, cosmetics, and appliances, organized into specialized departments under one roof.
-
B.
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.
-
C.
retail holding company
chosen
A retail holding company is a parent corporation that owns and oversees multiple retail businesses or brands, managing their strategic direction and financial performance while each operates as a separate entity.
-
D.
clothing retailer
A clothing retailer is a business that purchases apparel and related accessories from manufacturers or wholesalers and sells them directly to consumers through physical stores, online platforms, or both.
-
E.
luxury retail holding company
A luxury retail holding company is a corporate entity that owns, manages, and strategically coordinates a portfolio of high-end retail brands to maximize value, market presence, and operational synergies.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.