Triple
T19547731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers family |
E489118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian business dynasty |
C41821
|
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: Canadian business dynasty Context triple: [Rogers family, instanceOf, Canadian business dynasty]
-
A.
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.
-
B.
Canadian family
A Canadian family is a household unit in Canada typically composed of individuals related by blood, marriage, adoption, or long-term partnership, shaped by the country’s cultural diversity, social values, and legal frameworks.
-
C.
South Korean business family
A South Korean business family is a kinship-based group that owns, controls, or significantly influences one or more enterprises in South Korea, often blending familial authority with corporate governance and social status.
-
D.
Canadian private company
A Canadian private company is a for-profit corporation incorporated under Canadian law whose shares are not offered to the public and are typically held by a limited number of private shareholders.
-
E.
Scottish-Canadian family
A Scottish-Canadian family is a kinship group whose members share ancestral roots in Scotland and cultural, historical, or residential ties to Canada, often blending Scottish traditions with Canadian social and regional influences.
- F. None of above. chosen
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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:41 p.m.