Triple
T23503348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coats family |
E571915
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish industrial dynasty |
C37263
|
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: Scottish industrial dynasty Context triple: [Coats family, instanceOf, Scottish industrial dynasty]
-
A.
19th-century business family
A 19th-century business family is a kinship-based household whose members collectively own, manage, and pass down commercial enterprises, blending domestic life with entrepreneurial activity and social status in the context of industrializing economies.
-
B.
British industrial family
chosen
A British industrial family is a multigenerational household whose wealth, social standing, and identity are rooted in owning, managing, or significantly influencing industrial enterprises in Britain.
-
C.
Canadian business dynasty
A Canadian business dynasty is a powerful, multigenerational family whose members control or significantly influence major Canadian businesses, often shaping the country’s economic and social landscape over decades.
-
D.
Scottish landed family
A Scottish landed family is a historically established kin group that owns or once owned significant estates in Scotland, often holding social status, local influence, and sometimes hereditary titles tied to their ancestral lands.
-
E.
American business dynasty
A powerful, multigenerational American family whose wealth, influence, and identity are built around the ownership, control, and continuity of major business enterprises.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:06 p.m.