Triple
T21016146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minton, Hollins & Co. |
E517680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English company |
C3617
|
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: English company Context triple: [Minton, Hollins & Co., instanceOf, English company]
-
A.
British-Dutch company
A British-Dutch company is a business organization that is jointly rooted in and typically operates under the corporate, legal, and tax frameworks of both the United Kingdom and the Netherlands, often with dual headquarters or a historically binational structure.
-
B.
European company
A European company is a business entity legally registered and operating within one or more countries of Europe, subject to European and relevant national regulations, markets, and cultural contexts.
-
C.
19th-century British company
A 19th-century British company is a business organization established in Britain between 1801 and 1900, typically operating under early industrial capitalism, imperial trade networks, and evolving corporate and legal frameworks of the Victorian era.
-
D.
British brand
A British brand is a commercial identity originating from or strongly associated with the United Kingdom, characterized by its distinct heritage, design, and cultural values that reflect British traditions and lifestyle.
-
E.
British organisation
chosen
A British organisation is an entity based in or primarily operating within the United Kingdom, formed by individuals or groups to pursue specific social, cultural, economic, or political objectives under UK legal and regulatory frameworks.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:54 p.m.