Triple
T17502575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trafalgar House |
E426227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British conglomerate |
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: British conglomerate Context triple: [Trafalgar House, instanceOf, British conglomerate]
-
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.
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.
-
C.
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.
-
D.
Barbadian company
A Barbadian company is a legal business entity incorporated or registered under the laws of Barbados, typically benefiting from the country's regulatory, tax, and corporate governance framework.
-
E.
British businessperson
A British businessperson is an individual from the United Kingdom engaged in commercial, industrial, or professional business activities, typically involved in managing, owning, or operating enterprises for profit.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.