Triple
T15916328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast Retailing |
E385979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational retail 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: multinational retail holding company Context triple: [Fast Retailing, instanceOf, multinational retail holding 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.
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.
-
C.
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.
-
D.
luxury retail holding company
A luxury retail holding company is a corporate entity that owns, manages, and strategically coordinates multiple high-end retail brands or businesses under a unified financial and governance structure.
-
E.
big-box retailer
A big-box retailer is a large, warehouse-style store that offers a wide variety of goods at discounted prices, typically located in suburban areas and operated by a national or global chain.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.