Triple
T32333206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schermerhorn family |
E826104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York elite family |
C25203
|
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: New York elite family Context triple: [Schermerhorn family, instanceOf, New York elite family]
-
A.
member of a prominent New York family
chosen
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.
-
B.
Hudson River Valley family
A Hudson River Valley family is a multigenerational household or kinship group rooted in the Hudson River region, whose identity, traditions, and daily life are shaped by the valley’s distinctive history, landscape, and cultural influences.
-
C.
American real estate heir
An American real estate heir is an individual who inherits or is poised to inherit substantial wealth, property holdings, and business interests from a family-owned real estate empire in the United States.
-
D.
American show-business family
A family whose members are prominently involved in the American entertainment industry, often spanning multiple generations and professions such as acting, music, production, or management.
-
E.
American legal dynasty
A powerful, multigenerational American family whose members have held prominent roles in law, politics, and public service, shaping legal and political institutions over time.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:47 a.m.