Triple
T21469583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlan family |
E529688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American legal dynasty |
C44813
|
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: American legal dynasty Context triple: [Harlan family, instanceOf, American legal 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.
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.
-
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.
British-American family
A British-American family is a kinship group whose members and cultural identity are shaped by both British and American national, social, and historical influences.
-
E.
member of a prominent New York family
A member of a prominent New York family is an individual born into or formally affiliated with a socially, economically, or politically influential lineage based in New York, whose identity and opportunities are shaped by the family’s status, legacy, and network.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:16 p.m.